agentleFS
Sign inStart free
MasriyanMasriyan/gemini-security-skills/api-security-automation/SKILL.md

api-security-automation

Skill4 starsChanged 5 months agoMITView on GitHub

API security automation skill for REST, GraphQL, gRPC, and WebSocket APIs. Covers OpenAPI/AsyncAPI ingestion, authenticated fuzzing, OWASP API Top 10 (BOLA, BFLA, mass assignment, SSRF), schema diffing, GraphQL introspection abuse, JWT and OAuth misuse, rate-limit and replay testing. Use to automate API assessments with safe, scoped, evidence-backed findings.

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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:

    Avoid production write endpoints unless explicitly authorized.

    line 11

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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 Automation

Authorization Boundary

  • Require base URL, environment label (lab/staging/prod), scoped credentials, and rate ceiling.
  • Avoid production write endpoints unless explicitly authorized; prefer idempotent or staging traffic.
  • Strip tokens and PII from artifacts.

Testing Workflow

  1. Ingest spec: OpenAPI, GraphQL SDL, gRPC .proto, Postman collection, HAR; otherwise crawl with katana/hetty.
  2. Build a request matrix per endpoint × role × parameter class (id, enum, nested object, file).
  3. Auth tests: token tampering, alg=none, kid confusion, audience swap, refresh replay, scope downgrade.
  4. Object-level auth: enumerate IDs across roles to detect BOLA/IDOR.
  5. Function-level auth: invoke admin/owner endpoints with low-privilege tokens.
  6. Mass assignment: inject unexpected fields; observe persisted state changes.
  7. Input handling: type confusion, prototype pollution, SSRF via URL params, path traversal, deserialization.
  8. GraphQL: introspection, alias-based rate bypass, batched queries, depth/complexity DoS.
  9. Rate and replay: nonce reuse, idempotency-key collisions, race conditions on state.

Tooling

  • ffuf, wfuzz, nuclei (api templates), kiterunner, mitmproxy, hetty, graphql-cop, clairvoyance, jwt_tool, restler, schemathesis.

Output Contract

  • spec/: normalized spec snapshot.
  • requests/: replayable HAR per finding.
  • findings.jsonl: {endpoint, method, role, class, severity, evidence, cwe, remediation}.
  • report.md: business impact, top fixes, regression tests as CI hooks.

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