Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add Samurai-goose/SPECTER-The-Illusive-Security-Protocol --skill api-security-reviewgit clone --depth 1 https://github.com/Samurai-goose/SPECTER-The-Illusive-Security-ProtocolWrote 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.
[](https://agentmods.dev/skills/samurai-goose/specter-the-illusive-security-protocol/api-security-review)<a href="https://agentmods.dev/skills/samurai-goose/specter-the-illusive-security-protocol/api-security-review"><img src="https://agentmods.dev/badge/skills/samurai-goose/specter-the-illusive-security-protocol/api-security-review/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.
<a href="https://agentmods.dev/skills/samurai-goose/specter-the-illusive-security-protocol/api-security-review"><img src="https://agentmods.dev/badge/skills/samurai-goose/specter-the-illusive-security-protocol/api-security-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00041 | $0.02618 |
| Opus 5 | $0.00020 | $0.01309 |
| Sonnet 5 | $0.00008 | $0.00524 |
| Haiku 4.5 | $0.00004 | $0.00262 |
Grade B, and why
api-security-review scanned grade B with 1 finding 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 10d 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.
Cloud metadata endpointmediumServer-side request forgery
One request to 169.254.169.254 can return temporary IAM credentials.
- [ ] Test with internal IPs (`169.254.169.254`, `10.0.0.0/8`, `localhost`) as the callback URL Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
How it starts
The opening of the file, as written. The whole thing — 271 lines — stays where its author put it; the contents beside it link to each section on GitHub.
API Security Review
Purpose
Perform targeted security review of API endpoints. APIs present unique attack surface beyond standard web vulnerabilities: mass assignment, BOLA/BFLA, excessive data exposure, lack of rate limiting, and GraphQL-specific issues. This skill covers REST, GraphQL, WebSocket, and gRPC APIs.
Triggers
- API endpoints identified during recon analysis
- User requests API security review
- API documentation (OpenAPI/Swagger, GraphQL schema) available
- Code review identifies API route definitions
- New API version or endpoint deployed
Required Inputs
| Input | Description | Required |
|---|---|---|
governance_context |
Active engagement governance record | Yes |
api_target |
Base URL or API endpoint(s) | Yes |
api_type |
REST, GraphQL, WebSocket, gRPC | Auto-detected |
api_docs |
OpenAPI/Swagger spec, GraphQL schema, or proto files | Recommended |
auth_mechanism |
Bearer token, API key, OAuth, session cookie | Recommended |
source_code |
API route handlers and middleware | Recommended |
Workflow
-
Scope Verification — Confirm API target is within authorized scope.
-
API Discovery & Mapping — Enumerate:
- All endpoints (from docs, source code, or active discovery)
- HTTP methods per endpoint
- Request/response schemas
- Authentication requirements per endpoint
- Rate limiting configuration
- API versioning scheme
- For GraphQL: full schema introspection (queries, mutations, subscriptions, types)
-
OWASP API Security Top 10 (2023) Review:
API1: Broken Object-Level Authorization (BOLA)
- Test every endpoint that accepts object IDs
- Swap IDs between users: can user A access user B's objects?
- Test with sequential IDs, UUIDs, and encoded references
- Check bulk/list endpoints for data leakage
API2: Broken Authentication
- Test authentication on every endpoint (remove token, use expired token)
- Check for authentication bypass via parameter pollution
- Test token generation entropy and lifetime
- Verify logout actually invalidates tokens
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.
- 10d ago First seen · 271 lines · 41 tokens per session scan B 3e73abceddd6
api-security-review is a skill published in the GitHub repository Samurai-goose/SPECTER-The-Illusive-Security-Protocol (2 stars, last pushed 2mo ago), licensed MIT. It adds 41 tokens to every session and 2,618 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (cloud metadata endpoint). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…