api-testing

api-testing is a skill for Claude Code from ogrodev/fsociety. It costs 366 tokens per session (3,774 once invoked), scanned A, original, MIT.

A guide for testing application programming interfaces, or APIs: interfaces that let software exchange data and perform actions. It covers REST, GraphQL, gRPC, and WebSocket interfaces.

In plain words
What is it for?
Use it for API security reviews, including documentation analysis, endpoint discovery, schema inspection, fuzzing, token testing, authorization checks, and rate-limit testing.
Why use it?
It provides a method for finding endpoints and checking authentication, permissions, input handling, business rules, and request limits.

Skill for Claude Code

Written for Claude Code: ${CLAUDE_PLUGIN_ROOT} variable.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the elliot plugin — 9 skills, 24 commands, 2 agents, 4 hooks shipped together

Good fit Use it for API security reviews, including documentation analysis, endpoint discovery, schema inspection, fuzzing, token testing, authorization checks, and rate-limit testing.

Compare 6 skills from other repositories ↓
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add ogrodev/fsociety
Claude Code
/plugin install elliot

Made for: Claude Code.

Or install elliot, the plugin that ships this one along with the rest of its 9 skills, 24 commands, 2 agents, 4 hooks.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for api-testing

README.md
[![agentmods](https://agentmods.dev/badge/skills/ogrodev/fsociety/api-testing/github.svg)](https://agentmods.dev/skills/ogrodev/fsociety/api-testing)
Your own site
<a href="https://agentmods.dev/skills/ogrodev/fsociety/api-testing"><img src="https://agentmods.dev/badge/skills/ogrodev/fsociety/api-testing/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for api-testing

Your own site · 80×15
<a href="https://agentmods.dev/skills/ogrodev/fsociety/api-testing"><img src="https://agentmods.dev/badge/skills/ogrodev/fsociety/api-testing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 366 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,774 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00366 $0.03774
Opus 5.5 $0.00146 $0.01510
Sonnet 5.5 $0.00073 $0.00755
Haiku 4.5 $0.00037 $0.00377

Measured 2mo ago against content hash 28c70fb125b4, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

api-testing scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

elliot/skills/api-testing/SKILL.md · 306 lines

How it starts

The opening of the file, as written. The whole thing — 306 lines — stays where its author put it; the contents beside it link to each section on GitHub.

API Security Testing

API testing is the most target-rich domain in modern application security. REST, GraphQL, gRPC, and WebSocket interfaces expose business logic directly, often with weaker controls than their web UI counterparts. This skill covers the full API attack lifecycle -- from endpoint discovery and authentication analysis through injection, authorization abuse, business logic exploitation, and rate limit bypass.

Attack Surface Decision Tree

Before diving into testing, classify the API type and prioritize your approach.

Is there API documentation (Swagger/OpenAPI/GraphQL introspection)?
├── YES → Start with documented endpoints, then hunt for undocumented ones
│   ├── REST with OpenAPI → Parse spec, test every endpoint/method/parameter
│   ├── GraphQL with introspection → Dump schema, map all queries/mutations/subscriptions
│   └── gRPC with reflection → List services, extract .proto definitions
└── NO → Start with endpoint discovery and fingerprinting
    ├── Known web app → Spider + JS analysis + API path brute-force
    ├── Mobile app → Decompile APK/IPA, extract API calls and endpoints
    └── Unknown target → Port scan + service fingerprint + path fuzzing

What authentication mechanism is used?
├── JWT → jwt-attacks.md (alg:none, key confusion, claim manipulation)
├── OAuth2/OIDC → oauth-attacks.md (PKCE bypass, token theft, redirect manipulation)
├── API Key → Test key scope, rotation, leakage in logs/responses/JS
├── Session cookie → Standard session attacks (fixation, prediction, theft)
├── mTLS → Certificate validation bypass, weak CA trust
└── None / Optional → Test if auth is truly enforced on all endpoints

What is the primary risk?
├── Data exposure → Focus on BOLA/IDOR, mass data retrieval, excessive data exposure
├── Privilege escalation → Focus on auth bypass, BFLA, role manipulation
├── Injection → Focus on SQLi, NoSQLi, command injection, SSTI through API params
├── Business logic → Focus on race conditions, mass assignment, workflow bypass
└── Availability → Focus on rate limiting, GraphQL DoS, resource exhaustion

Read the full file on GitHub · 306 lines

Files

What ships with it

8 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2mo ago First seen · 306 lines · 366 tokens per session scan A 28c70fb125b4

Subscribe to this mod's changes

api-testing is a skill published in the GitHub repository ogrodev/fsociety (20 stars, last pushed 7mo ago), licensed MIT. It adds 366 tokens to every session and 3,774 once invoked, about $0.0015 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

common-appsec-patterns

Application security testing coordinator for common vulnerability patterns including XSS, injection flaws, and client-side security issues. Orchestrates specialized testing agents to identify and validate common application security weaknesses.

Stickman230/claude-pentest · 42 tokens

cve-testing

CVE vulnerability testing coordinator that identifies technology stacks, researches known vulnerabilities, and tests applications for exploitable CVEs using public exploits and proof-of-concept code.

Stickman230/claude-pentest · 36 tokens

api-31-idor

IDOR (Insecure Direct Object Reference) testing checklist: object ID enumeration, horizontal/vertical privilege escalation, GUID predictability, indirect references via hashes, chained IDOR, and API endpoint IDOR. Use for web app pentests and bug bounty IDOR discovery.

vigilantshield/Claude-HunterKit · 60 tokens

api-22-business-logic

Business logic vulnerability testing for web/mobile/API engagements. Covers workflow bypass, state machine violations, multi-step process abuse, price/quantity/discount manipulation, currency confusion, coupon stacking, refund/chargeback abuse, race conditions on logic boundaries, parameter tampering for hidden flows…

vigilantshield/Claude-HunterKit · 136 tokens

api-02-api-doc-leakage

API documentation leakage testing skill. Covers exposed Swagger/OpenAPI endpoints, debug endpoints, internal API documentation, GraphQL introspection, and sensitive information in API responses. Use when searching for unintended API documentation exposure.

vigilantshield/Claude-HunterKit · 50 tokens

api-21-mtls

Mutual TLS (mTLS) security testing skill. Covers certificate validation bypass, client certificate spoofing, mTLS downgrade attacks, and certificate pinning bypass. Use when testing mTLS implementations.

vigilantshield/Claude-HunterKit · 45 tokens