Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/Morningstar202604/awesome-skillkitnpx agentmods add skills/morningstar202604/awesome-skillkit/api-test-suite-builderWrote 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/morningstar202604/awesome-skillkit/api-test-suite-builder)<a href="https://agentmods.dev/skills/morningstar202604/awesome-skillkit/api-test-suite-builder"><img src="https://agentmods.dev/badge/skills/morningstar202604/awesome-skillkit/api-test-suite-builder/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/morningstar202604/awesome-skillkit/api-test-suite-builder"><img src="https://agentmods.dev/badge/skills/morningstar202604/awesome-skillkit/api-test-suite-builder.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.00098 | $0.02245 |
| Opus 5.5 | $0.00039 | $0.00898 |
| Sonnet 5.5 | $0.00020 | $0.00449 |
| Haiku 4.5 | $0.00010 | $0.00225 |
Grade A, and why
api-test-suite-builder 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 1mo 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.
This is a copy
95% identical to api-test-suite-builder — 201 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
API Test Suite Builder
Scans API route definitions across frameworks (Next.js App Router, Express, FastAPI, Django REST) and generates a runnable test suite — Vitest+Supertest (Node) or Pytest+httpx (Python) — covering auth, input validation, error codes, pagination, file upload, and rate limiting.
Input Checklist
| Input | Required | Description |
|---|---|---|
| Project root | Yes | Path to the repo containing the API route definitions |
| Framework | Yes | next-app-router / express / fastapi / django-rest (if unsure, step 1's probe commands decide it) |
| Test stack | Yes | vitest+supertest (Node) or pytest+httpx (Python) |
| Output location | No | The directory for test files; defaults to project convention (tests/ or __tests__/) |
| Generation scope | No | All routes or a specified route group; defaults to all |
When inputs are missing, ask for all at once: "Please provide: (1) the project root; (2) the test stack (Vitest+Supertest or Pytest+httpx); (3) whether to generate only some routes. If the framework is unclear, I'll decide it with probe commands first."
Pre-flight Checks
Run each in turn; on any failure → apply the fix, then STOP:
# 1. The project directory exists
ls <project-root> > /dev/null && echo OK
# Expected: OK. On failure → confirm the path with the user, STOP.
# 2. Probe for framework signals (at least one hits)
ls <project-root>/package.json <project-root>/requirements.txt <project-root>/pyproject.toml 2>/dev/null
# Expected: at least one file listed. If all are missing → confirm this is an API project, STOP.
# 3. The test runner is available
node --version || python3 --version
# Expected: prints a version. On failure → test-file generation is unaffected, but note to the user that local verification isn't possible.
Workflow
Step 1: Probe routes
Run the probe command for the corresponding framework (in the project root):
Next.js App Router
find ./app/api -name "route.ts" -o -name "route.js" | sort
grep -rn "export async function\|export function" app/api/**/route.ts | \
grep -oE "(GET|POST|PUT|PATCH|DELETE|HEAD|OPTIONS)" | sort -u
find ./app/api -name "route.ts" | while read f; do
route=$(echo $f | sed 's|./app||' | sed 's|/route.ts||')
methods=$(grep -oE "export (async )?function (GET|POST|PUT|PATCH|DELETE)" "$f" | \
grep -oE "(GET|POST|PUT|PATCH|DELETE)")
echo "$methods $route"
done
What ships with it
1 file 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.
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.
- 1mo ago Changed · +33 tokens per session f5ce90b08f7c
- 1mo ago Changed · -16 lines · +36 tokens per session 00e778b98199
- 1mo ago First seen · 183 lines · 29 tokens per session scan A 16ff1453f6b5
api-test-suite-builder is a skill published in the GitHub repository Morningstar202604/awesome-skillkit (0 stars, last pushed 25d ago), licensed Apache-2.0. It adds 98 tokens to every session and 2,245 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 95% identical to api-test-suite-builder, differing in 201 lines, and is treated as a copy.
Other skills, from other repositories
systematic-debugging
4-phase root cause debugging: understand bugs before fixing.
react-patterns
React 18/19 patterns including hooks discipline, server/client component boundaries, Suspense + error boundaries, form actions, data fetching, state management decision trees, and accessibility-first composition. Use when writing or reviewing React components.
golang-testing
Go testing best practices including table-driven tests, test helpers, benchmarking, race detection, coverage analysis, and integration testing patterns. Use when writing or improving Go tests.
verification-loop
A comprehensive verification system for Claude Code sessions. Use when verifying a Claude Code session's work before claiming it is complete.
mem0-test-integration
Verify a Mem0 integration produced by /mem0-integrate. Runs in the same workspace on the same branch (loose coupling) — installs dependencies, runs the repo's native test suite, then exercises a real end-to-end smoke flow against the user's API key. Produces a scorecard. TRIGGER when: user has just run /mem0-integrate…
darwinian-evolver
Evolve prompts/regex/SQL/code with Imbue's evolution loop.