agentleFS
Sign inStart free
gl1tch0x1gl1tch0x1/SecAgent/skills/APIAssessment/SKILL.md

APIAssessment

Skill2 starsChanged 44 days agoMITView on GitHub

Use OpenAPI definitions and captured requests as method-preserving inventory. Keep path, query, body shape, content type, and authentication context together. Return exact request and response metadata with secrets redacted. Mark missing identities, state contracts, or replay evidence as coverage gaps.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are 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.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use OpenAPI definitions and captured requests as method-preserving inventory.

    line 3
  2. Distinctive:

    Treat GraphQL fields and mutations as distinct operations.

    line 11

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

Use OpenAPI definitions and captured requests as method-preserving inventory. Keep path, query, body shape, content type, and authentication context together.

Hunting workflow

  1. Identify resources and object identifiers, then map which roles can read and change each resource.
  2. Compare an authorized request with a separate identity and a deliberately unauthorized object. Do not call a 200 response an authorization bypass without checking the returned object's ownership and state.
  3. Trace alternate representations and API versions for the same resource. Compare server-side authorization, not merely client-side UI controls.
  4. Inspect pagination, filtering, export and batch endpoints for inconsistent object checks using bounded requests.
  5. Treat GraphQL fields and mutations as distinct operations. Preserve operation names, variables and query depth in the inventory.
  6. Probe POST, PUT, PATCH and DELETE only when the operator supplies a state read, negative control and cleanup procedure. Stop on unexpected state changes.

Return exact request and response metadata with secrets redacted. Mark missing identities, state contracts, or replay evidence as coverage gaps.

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