persona
Skill1 starsChanged 3 months agoMITView on GitHub
12 other projects use a version of this.
Adopted by
Most recently taken up by
- zrosenbauer/skillstheir own version, first seen Nov 1, 2026
- LuciferDono/personatheir own version, first seen Oct 20, 2026
- mehrad-dm/mastermindtheir own version, first seen Oct 13, 2026
- akachandan1/proofstacktheir own version, first seen Oct 11, 2026
- 47096/personatheir own version, first seen Sep 23, 2026
- stritar/skillstheir own version, first seen Sep 11, 2026
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.
AnthropicSkillanalyze
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
Other versions12 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 12
- Mehdibargach/claude-code-pm-skills★ 97same name
- rainday/smart-blog-skills★ 35same name
- mehrad-dm/mastermind★ 23same name
- duguobao812718-wq/persona-skill★ 4same name
- tatertot365/claude-persona-plugin★ 3same name
- cacardinal/laila★ 1same name
- takotyan00/claude-code-life★ 1same name
- zrosenbauer/skills★ 1same name
- 47096/persona★ 0same name
- akachandan1/proofstack★ 0same name
2 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository50 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .claude/CLAUDE.mdCLAUDE.md
- CLAUDE.mdCLAUDE.md
- agent-safetySkill
- ai-llmSkill
- apiSkill
- asset-graphSkill
- authSkill
- auto-researchSkill
- binary-analysisSkill
- business-logicSkill
- campaignSkill
- cicd-securitySkill
- cloudSkill
- cors-csrfSkill
- coverageSkill
- cross-accountSkill
- domain-modelSkill
- enrichmentSkill
- evaluation-harnessSkill
- file-uploadSkill
- graphql-auditSkill
- http-protocolSkill
- identity-domainSkill
- impact-verifierSkill
- meme-coin-auditSkill
- mobileSkill
- modern-browserSkill
- nuclei-scannerSkill
- oob-infraSkill
- osintSkill
- plannerSkill
- privescSkill
- program-memorySkill
- race-conditionSkill
- rceSkill
- reconSkill
- reportingSkill
- sastSkill
- scope-managerSkill
- skill-scientistSkill
- sqliSkill
- ssrfSkill
- standard-catalogSkill
- technique-kbSkill
- traffic-corpusSkill
- triage-validationSkill
- vuln-intelSkill
- web3-auditSkill
- xssSkill
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
- Very specific: line 16
Before reporting: run redact-secrets to produce report-safe manifests.
“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.
Files
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, thenimport-cookiefor each account, thenvalidate-sessions. - Reusing prior sessions: run
validate-sessionsto confirm they still work, thenexport-headers. - Before reporting: run
redact-secretsto produce report-safe manifests.
Available Workflows
| Workflow | Purpose |
init-personas | Create persona manifest template for the current engagement. |
import-cookie | Import a cookie, bearer token, API key, or header set for one persona. |
validate-sessions | Request a known URL as each persona and classify auth state. |
redact-secrets | Produce safe redacted manifest for reports and logs. |
export-headers | Generate 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)
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
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.

