This skill should be used when the user asks to "test for broken authentication vulnerabilities", "assess session management security", "perform credential stuffing tests", "evaluate password policies", "test for session fixation", or "identify authentication bypass flaws". It provides comprehensive techniques for identifying authentication and session management weaknesses in web applications.
4k tokens
context cost
the whole folder, loaded on every use
24
files
instructions only
0
copies elsewhere
how many repositories repackaged it
505
stars on the repo
on the repository, not the skill itself
Install
one command, takes just this skill from the repository
Identify and exploit authentication and session management vulnerabilities in web applications. Broken authentication consistently ranks in the OWASP Top 10 and can lead to account takeover, identity theft, and unauthorized access to sensitive systems. This skill covers testing methodologies for password policies, session handling, multi-factor authentication, and credential management.
Prerequisites
🧠 Knowledge Modules (Fractal Skills)
1. Required Knowledge
2. Required Tools
3. Required Access
4. Phase 1: Authentication Mechanism Analysis
5. Phase 2: Password Policy Testing
6. Phase 3: Credential Enumeration
7. Phase 4: Brute Force Testing
8. Phase 5: Credential Stuffing
9. Phase 6: Session Management Testing
10. Phase 7: Session Fixation Testing
11. Phase 8: Session Timeout Testing
12. Phase 9: Multi-Factor Authentication Testing
13. Phase 10: Password Reset Testing
14. Common Vulnerability Types
15. Credential Testing Payloads
16. Session Cookie Flags
17. Rate Limiting Bypass Headers
18. Legal Requirements
19. Technical Limitations
20. Scope Considerations
21. Example 1: Account Lockout Bypass
22. Example 2: JWT Token Attack
23. Example 3: Password Reset Token Exploitation
How to use it
Copy the folder
Take dokhacgiakhoa/broken authentication testing from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
Check the name does not clash
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.