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 charlieviettq/awesome-agent-skill --skill api-security-testinggit clone --depth 1 https://github.com/charlieviettq/awesome-agent-skillWrote 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/charlieviettq/awesome-agent-skill/api-security-testing)<a href="https://agentmods.dev/skills/charlieviettq/awesome-agent-skill/api-security-testing"><img src="https://agentmods.dev/badge/skills/charlieviettq/awesome-agent-skill/api-security-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.
<a href="https://agentmods.dev/skills/charlieviettq/awesome-agent-skill/api-security-testing"><img src="https://agentmods.dev/badge/skills/charlieviettq/awesome-agent-skill/api-security-testing.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.00045 | $0.00438 |
| Opus 5 | $0.00023 | $0.00219 |
| Sonnet 5 | $0.00009 | $0.00088 |
| Haiku 4.5 | $0.00005 | $0.00044 |
Grade A, and why
api-security-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 9d 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.
What it actually says
API security testing
Preconditions
- Test in non-production unless explicitly authorized.
- Use dedicated test accounts; never real customer PII in payloads.
Test matrix (prioritized)
Authentication and session
- Missing/invalid token rejected (401)
- Expired or revoked credentials rejected
- Session fixation / cookie flags (HttpOnly, Secure, SameSite) where applicable
Authorization
- Horizontal: user A cannot access user B's resource IDs
- Vertical: non-admin cannot invoke admin routes
- IDOR on path/query/body identifiers
Input and abuse
- Oversized payloads rejected
- Injection surfaces parameterized (SQL, command, template)
- Rate limiting on auth and expensive endpoints
Data exposure
- Errors do not leak stack traces or secrets in prod-like config
- Responses omit internal fields (tokens, hashes, full PAN)
- Pagination does not bypass auth filters
Transport and config
- HTTPS enforced; HSTS where applicable
- CORS not
*with credentials - Security headers on API gateway if present
Web-facing surfaces (when API serves or pairs with UI)
- CSP or explicit script policy documented
- CSRF protection on cookie-based mutations
- Clickjacking headers (
X-Frame-Optionsor CSPframe-ancestors) where relevant - File upload: type/size limits, virus scan hook if required by policy
Reporting
For each finding: endpoint, steps, impact, severity, remediation, retest status.
Boundaries
- Defensive testing only; no unauthorized production scanning.
- For deep pen-test, engage formal AppSec process.
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.
- 9d ago First seen · 61 lines · 45 tokens per session scan A 79da477c8928
api-security-testing is a skill published in the GitHub repository charlieviettq/awesome-agent-skill (25 stars, last pushed 1mo ago), licensed MIT. It adds 45 tokens to every session and 438 once invoked, about $0.0002 per session on Opus 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-09-03.
Other skills, from other repositories
api-tester
A tool for creating and checking API tests from the real API contract and implementation. An API is the agreed way that software sends requests and receives responses.
ash-framework
Ash Framework — resources, actions, policies, aggregates, calculations, AshPhoenix.Form, LiveView, migrations. Use when generating resources via mix ash.codegen, editing changes, checks, types, validations, or domain code interfaces.
deploy
Elixir/Phoenix deployment patterns — Dockerfile, fly.toml, runtime.exs, mix release, rel/ overlays. Use when configuring Fly.io, Docker, CI/CD, health checks, or production migrations.
liveview-patterns
Build LiveView: async data (assignasync), PubSub (check connected?), phx-change events, form components/modals/uploads, streams for lists, livepatch. Use when handling interactions, debugging events, or tracking Presence.
tidewave-integration
Tidewave MCP runtime tools — debugging, smoke testing, live state inspection, SQL queries, hex docs. Use when evaluating code in a running Phoenix app.
oban
Oban job processing — workers, perform/1 (OSS) and process/1 (Pro), queues, cron, retries, unique jobs, idempotency, Oban Pro (Workflow, Batch, Chunk, Smart Engine), Testing. Use when writing Oban workers, queue config, or debugging jobs.