agentleFS
JustineDevsJustineDevs/premortem/.agents/skills/auth-sec/SKILL.md

auth-sec

Skill2 starsChanged 5 months agoApache-2.0View on GitHub

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.

2 other projects use a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    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:

    Use it to decide whether the issue is mainly login mechanics, object-level authorization, browser trust boundaries, or identity protocols …

    line 13
  2. Distinctive:

    If enterprise federation exists, continue with OAuth, OIDC, or SAML topics

    line 36
  3. Distinctive:

    Default credentials, username variants, wordlist sizing, and port focus are consolidated in authbypass-authentication-flaws

    line 41

≈ “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.

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

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: login bypass, password reset, 2FA, enumeration, brute-force protections
  • IDOR Broken Object Authorization: IDOR, BOLA, BFLA, missing object permissions
  • JWT OAuth Token Attacks: algorithm confusion, key trust issues, claim abuse, token forgery
  • OAuth OIDC Misconfiguration: redirect URI, state, nonce, PKCE, account binding
  • CSRF Cross Site Request Forgery: CSRF tokens, SameSite, JSON CSRF, login CSRF
  • CORS Cross Origin Misconfiguration: reflected Origin, credentialed cross-origin reads, allowlist bypass
  • SAML SSO Assertion Attacks: 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
  • Default credentials, username variants, wordlist sizing, and port focus are consolidated in authbypass-authentication-flaws

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.