api-sec — Claude Code skill: what it does, how to install
Routes API security testing across REST, GraphQL, and mobile backends. Helps an agent choose the right testing track before running deep checks.
npx skills add yaklang/hack-skills --skill api-sec -a claude-codeWhat api-sec does
This skill acts as an entry triage router for API security assessments. When an agent identifies Swagger files, bearer tokens, or GraphQL queries, api-sec maps those signals directly to focused assessment tracks. It establishes an explicit order. Arbitrary probing stops here.
The routing logic relies on a triage matrix and a four-step flow. Recon and documentation drift route to api-recon-and-docs. Object-level flaws and BOLA go to api-authorization-and-bola. Tokens, header trust, and rate limits route to api-auth-and-jwt-abuse, while schema introspection shifts to graphql-and-hidden-parameters.
The skill does not execute vulnerability exploits directly. It functions purely as a classification router: without the deeper topic skills from the repository, the agent cannot proceed past the triage stage.
What it helps with
- prioritize security testing tracks across REST and GraphQL targets
- route authorization flaws and BOLA checks when IDs are detected
- assign token and rate-limit bypass investigations
- isolate GraphQL schema introspection and hidden parameter testing
Example prompts for the agent
- We found an OpenAPI spec and several JSON endpoints. Plan our test sequence with api-sec.
- The mobile API returns JWTs and exposes GraphQL. Which track should we run first?
- Profile updates accept undocumented fields. Route this issue according to api-sec.
How to install api-sec
1Skills CLI (Vercel)
npx skills add yaklang/hack-skills --skill api-sec -a claude-code2Manually: put the files in place
~/.claude/skills/api-sec/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/api-sec/
1Skills CLI (Vercel)
npx skills add yaklang/hack-skills --skill api-sec -a codex2Manually: put the files in place
.agents/skills/api-sec/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add yaklang/hack-skills --skill api-sec -a cursor2Manually: put the files in place
.cursor/skills/api-sec/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install yaklang/hack-skills api-sec2Manually: put the files in place
.github/skills/api-sec/SKILL.md1Skills CLI (Vercel)
npx skills add yaklang/hack-skills --skill api-sec -a gemini-cli2Platform CLI
gemini skills install https://github.com/yaklang/hack-skills --path skills/api-secManually: put the files in place
.devin/skills/api-sec/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add yaklang/hack-skills --skill api-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 api-sec
How to install api-sec in Claude Code?
Run npx skills add yaklang/hack-skills --skill api-sec -a claude-code in your terminal. The file is installed at ~/.claude/skills/api-sec/SKILL.md.
What does the api-sec skill do?
It acts as an entry routing point for API security assessments. The skill evaluates traffic indicators like Swagger, tokens, or batching, then sends the agent to dedicated sub-skills.
Does api-sec execute vulnerability scans directly?
No, it only sets testing priorities and workflow tracks. Actual vulnerability checks for BOLA, token claims, or GraphQL batching require deeper topic skills from the repository.
Source text
SKILL.md · MIT
--- name: api-sec description: >- 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. --- # 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](../api-recon-and-docs/SKILL.md): OpenAPI, Swagger, version drift, hidden documentation - [API Authorization and BOLA](../api-authorization-and-bola/SKILL.md): BOLA, BFLA, method abuse, hidden writable fields - [API Auth and JWT Abuse](../api-auth-and-jwt-abuse/SKILL.md): bearer token, header trust, claim abuse, rate-limit bypass - [GraphQL and Hidden Parameters](../graphql-and-hidden-parameters/SKILL.md): introspection, batching, undocumented fields, hidden parameters ## Quick Triage | Observation | Route | |---|---| | Swagger or OpenAPI is present | [api-recon-and-docs](../api-recon-and-docs/SKILL.md) | | IDs appear in URL, JSON, headers, or GraphQL args | [api-authorization-and-bola](../api-authorization-and-bola/SKILL.md) | | JWT token visible in traffic | [api-auth-and-jwt-abuse](../api-auth-and-jwt-abuse/SKILL.md) | | `/graphql` or batched JSON arrays are present | [graphql-and-hidden-parameters](../graphql-and-hidden-parameters/SKILL.md) | | Registration, login, or profile updates accept extra fields | [api-authorization-and-bola](../api-authorization-and-bola/SKILL.md) then [api-auth-and-jwt-abuse](../api-auth-and-jwt-abuse/SKILL.md) | ## 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](../auth-sec/SKILL.md) - [business-logic-vuln](../business-logic-vuln/SKILL.md) - [recon-for-sec](../recon-for-sec/SKILL.md)
© yaklang · MIT · yaklang/hack-skills