identity-auth
Skill159 starsChanged 52 days agoMITView on GitHub
Test identity, authentication, authorization, and sessions.
In this repository7 other files it gives its agents.
- AGENTS.mdAGENTS.md
- api-testingSkill
- business-logicSkill
- llm-securitySkill
- misconfigSkill
- pentestSkill
- web-appSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 22
Do not use for general API inventory or business workflow flaws unless an identity boundary is the root cause.
- Distinctive: line 37
Use authorized disposable accounts and compare unauthenticated, low-privilege, and authorized contexts.
- Distinctive: line 39
Treat a changed status code alone as a candidate.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Identity, Authentication, and Authorization Testing
On-demand skill for identity-management, authentication, authorization, session, and cryptographic-control testing. The pentest orchestrator routes here when a finding candidate crosses an identity or authorization boundary. Load only the applicable playbook.
When to Use
- A login, registration, password-reset, MFA, session, token, role, or object-ownership boundary is in scope.
- Multiple users or privilege levels are available for differential testing.
- Do not use for general API inventory or business workflow flaws unless an identity boundary is the root cause.
Playbook Routing
| Class | Playbook |
| Authentication Bypass | playbooks/auth-bypass.md |
| IDOR / Broken Object-Level Authorization | playbooks/idor-access-control.md |
| JWT / Token Attacks | playbooks/jwt-attacks.md |
| CSRF | playbooks/csrf.md |
| Unvalidated Redirect | playbooks/redirects-unvalidated.md |
| Cryptographic Issues | playbooks/cryptographic-issues.md |
Common Pitfalls
- Use authorized disposable accounts and compare unauthenticated, low-privilege, and authorized contexts.
- Redact credentials, sessions, and token values in all artifacts.
- Treat a changed status code alone as a candidate; capture the protected resource or state differential needed to prove impact.
Verification Checklist
- Engagement bootstrap and scope validation succeeded.
- The matched playbook alone was loaded and bound to the PTT task.
- Evidence includes the two relevant identity or authorization contexts.
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.