agentleFS
zyphr-labszyphr-labs/bounty-harness/.claude/skills/persona/SKILL.md

persona

Skill1 starsChanged 3 months agoMITView on GitHub

12 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use analyze.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • AnthropicSkill

    analyze

    Answer data questions -- from quick lookups to full analyses. Use when looking up a single metric, investigating what's driving a trend or drop, comparing segments over time, or preparing a formal data report for stakeholders.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 10 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Before reporting: run redact-secrets to produce report-safe manifests.

    line 16

“Common” is measured: kept by at least 6 in 10 of the 10 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Persona

Overview

Manage authenticated testing personas (attacker, victim, admin, readonly, etc.) with secure credential storage, session validation, and per-persona header export for replay-based security testing.

Quick Reference

  • Skill: persona
  • Version: 1.0.0
  • Bounded Context: PersonaContext
  • Required tools: python3, curl, jq, openssl
  • Risk tier: destructive-manual (stores real credentials)

Workflow Selection

  • New program with accounts: start with init-personas, then import-cookie for each account, then validate-sessions.
  • Reusing prior sessions: run validate-sessions to confirm they still work, then export-headers.
  • Before reporting: run redact-secrets to produce report-safe manifests.

Available Workflows

WorkflowPurpose
init-personasCreate persona manifest template for the current engagement.
import-cookieImport a cookie, bearer token, API key, or header set for one persona.
validate-sessionsRequest a known URL as each persona and classify auth state.
redact-secretsProduce safe redacted manifest for reports and logs.
export-headersGenerate per-persona replay headers for consumption by other skills.

Evidence Required

  • Credential files stored under $OUTDIR/persona/creds/ (gitignored).
  • Redacted manifests show hashed identifiers only.
  • Session validation logs confirm active/inactive/partial auth state.

References

  • OWASP WSTG-ATHN-01 through WSTG-ATHN-10
  • OWASP ASVS V2 (Authentication)
  • OWASP ASVS V4 (Access Control)

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.