auth-sec — Claude Code skill: what it does, how to install
Entry P1 category router for authentication and authorization testing. Helps choose the right audit path before digging into specific attacks.
npx skills add yaklang/hack-skills --skill auth-sec -a claude-codeWhat auth-sec does
The skill serves as a P1 routing entry point for login flows, sessions, and authorization boundaries. It decides whether to prioritize authentication mechanics, object-level checks, or identity protocols. That keeps the audit focused.
The recommended sequence follows four clear stages. First, the agent confirms the authentication model and session boundaries. Next, it validates object-level and function-level access permissions. It then examines tokens, CORS, and CSRF before moving to federation mechanisms like OAuth, OIDC, or SAML.
This skill only routes between specialized topics from the repository and does not run exploits directly. Skipping this triage step causes agents to jump straight into protocol attacks while missing fundamental permission flaws.
What it helps with
- prioritize testing between authentication logic and object authorization
- route security audits to specific subtopics like JWT, OAuth, or SAML
- structure assessments covering login bypass, IDOR, CORS, and CSRF
Example prompts for the agent
- Check our login and session flows and decide what to test first
- We have OAuth and JWT tokens in use, run auth-sec to route the security check
- Plan an assessment for broken object authorization and session boundaries
How to install auth-sec
1Skills CLI (Vercel)
npx skills add yaklang/hack-skills --skill auth-sec -a claude-code2Manually: put the files in place
~/.claude/skills/auth-sec/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/auth-sec/
1Skills CLI (Vercel)
npx skills add yaklang/hack-skills --skill auth-sec -a codex2Manually: put the files in place
.agents/skills/auth-sec/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add yaklang/hack-skills --skill auth-sec -a cursor2Manually: put the files in place
.cursor/skills/auth-sec/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install yaklang/hack-skills auth-sec2Manually: put the files in place
.github/skills/auth-sec/SKILL.md1Skills CLI (Vercel)
npx skills add yaklang/hack-skills --skill auth-sec -a gemini-cli2Platform CLI
gemini skills install https://github.com/yaklang/hack-skills --path skills/auth-secManually: put the files in place
.devin/skills/auth-sec/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add yaklang/hack-skills --skill auth-sec -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about auth-sec
How to install auth-sec in Claude Code?
Run npx skills add yaklang/hack-skills --skill auth-sec -a claude-code in your terminal. The file will be placed at ~/.claude/skills/auth-sec/SKILL.md.
What does the auth-sec skill do?
It acts as a P1 entry router for authentication and authorization assessments. It helps pick the right testing path before invoking deeper topic-specific skills.
What is the recommended testing flow in auth-sec?
Confirm the authentication model and session boundaries first. Then verify object and function permissions, check tokens and cross-origin settings, and finish with federation protocols.
Source text
SKILL.md · MIT
--- name: auth-sec description: >- Entry P1 category router for authentication and authorization. Use when testing login flows, sessions, object authorization, JWT, OAuth, CORS, CSRF, and enterprise SSO weaknesses before any deeper auth topic skill. --- # Authentication and Authorization Router This is the routing entry point for authentication, sessions, and authorization boundaries. Use it to decide whether the issue is mainly login mechanics, object-level authorization, browser trust boundaries, or identity protocols such as OAuth/JWT/SAML before going deeper. ## When to Use - The target includes login, registration, password reset, 2FA, sessions, JWT, OAuth, or SSO - You suspect object authorization flaws, cross-tenant access, cross-origin reads, CSRF, or protocol misconfiguration - You need to decide whether to test authentication or authorization first ## Skill Map - [Authentication Bypass](../authbypass-authentication-flaws/SKILL.md): login bypass, password reset, 2FA, enumeration, brute-force protections - [IDOR Broken Object Authorization](../idor-broken-object-authorization/SKILL.md): IDOR, BOLA, BFLA, missing object permissions - [JWT OAuth Token Attacks](../jwt-oauth-token-attacks/SKILL.md): algorithm confusion, key trust issues, claim abuse, token forgery - [OAuth OIDC Misconfiguration](../oauth-oidc-misconfiguration/SKILL.md): redirect URI, state, nonce, PKCE, account binding - [CSRF Cross Site Request Forgery](../csrf-cross-site-request-forgery/SKILL.md): CSRF tokens, SameSite, JSON CSRF, login CSRF - [CORS Cross Origin Misconfiguration](../cors-cross-origin-misconfiguration/SKILL.md): reflected Origin, credentialed cross-origin reads, allowlist bypass - [SAML SSO Assertion Attacks](../saml-sso-assertion-attacks/SKILL.md): assertion wrapping, signature validation, audience, ACS boundaries ## Recommended Flow 1. First confirm the authentication model and session boundaries 2. Then confirm object-level and function-level authorization 3. Then move to token, cross-origin, and protocol details 4. If enterprise federation exists, continue with OAuth, OIDC, or SAML topics ## Related Categories - [api-sec](../api-sec/SKILL.md) - Default credentials, username variants, wordlist sizing, and port focus are consolidated in [authbypass-authentication-flaws](../authbypass-authentication-flaws/SKILL.md)
© yaklang · MIT · yaklang/hack-skills
