agentleFS
Sign inStart free
JustineDevsJustineDevs/premortem/.agents/skills/api-sec/SKILL.md

api-sec

Skill2 starsChanged 5 months agoApache-2.0View on GitHub

Entry P1 category router for API security. Use when choosing between API recon, authorization, token abuse, and hidden-parameter workflows before any deeper API 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, 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
  1. Distinctive:

    Use this skill first to decide whether the API issue is mostly recon/docs, object authorization, token trust, or GraphQL/hidden parameters, …

    line 13
  2. Distinctive:

    Start with exposed endpoints and documentation assets

    line 40
  3. Distinctive:

    If GraphQL or complex JSON is present, continue with hidden fields and schema abuse

    line 43

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

API Security Router

This is the routing entry point for API security testing.

Use this skill first to decide whether the API issue is mostly recon/docs, object authorization, token trust, or GraphQL/hidden parameters, then route to a deeper topic skill.

When to Use

  • The target exposes REST APIs, mobile backends, or GraphQL endpoints
  • You need to define API testing order before going into specific topics
  • You want to handle object authorization, JWT, GraphQL, and hidden fields as separate tracks

Skill Map

  • API Recon and Docs: OpenAPI, Swagger, version drift, hidden documentation
  • API Authorization and BOLA: BOLA, BFLA, method abuse, hidden writable fields
  • API Auth and JWT Abuse: bearer token, header trust, claim abuse, rate-limit bypass
  • GraphQL and Hidden Parameters: introspection, batching, undocumented fields, hidden parameters

Quick Triage

ObservationRoute
Swagger or OpenAPI is presentapi-recon-and-docs
IDs appear in URL, JSON, headers, or GraphQL argsapi-authorization-and-bola
JWT token visible in trafficapi-auth-and-jwt-abuse
/graphql or batched JSON arrays are presentgraphql-and-hidden-parameters
Registration, login, or profile updates accept extra fieldsapi-authorization-and-bola then api-auth-and-jwt-abuse

Recommended Flow

  1. Start with exposed endpoints and documentation assets
  2. Then evaluate object-level and function-level authorization
  3. Then evaluate token, header, signature, and rate-limit boundaries
  4. If GraphQL or complex JSON is present, continue with hidden fields and schema abuse

Related Categories

  • auth-sec
  • business-logic-vuln
  • recon-for-sec

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.

Check your setup, free