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 agentmods add skills/amanning3390/hermeshub/api-buildernpx skills add amanning3390/hermeshub --skill api-buildergit clone --depth 1 https://github.com/amanning3390/hermeshubWrote 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/amanning3390/hermeshub/api-builder)<a href="https://agentmods.dev/skills/amanning3390/hermeshub/api-builder"><img src="https://agentmods.dev/badge/skills/amanning3390/hermeshub/api-builder.svg" alt="Measured on agentmods" 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 | $0.00041 | $0.00457 |
| Opus 5 | $0.00020 | $0.00229 |
| Sonnet 5 | $0.00008 | $0.00091 |
| Haiku 4.5 | $0.00004 | $0.00046 |
Grade A, and why
api-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 4d 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 Builder
End-to-end API design, scaffolding, and documentation.
When to Use
- User wants to create a new API
- User needs endpoints for a specific domain
- User wants OpenAPI/Swagger documentation
- User asks for API scaffolding or boilerplate
Procedure
- Gather requirements: resources, operations, auth model
- Design the API schema (resources, relationships, endpoints)
- Generate OpenAPI 3.0 spec
- Scaffold route handlers with validation
- Add error handling and middleware
- Generate documentation
- Create test fixtures
Supported Frameworks
- Express (Node.js): express + zod + swagger-jsdoc
- FastAPI (Python): automatic OpenAPI generation
- Flask (Python): flask-restx or flask-smorest
REST Conventions
- GET /resources — list all
- POST /resources — create one
- GET /resources/:id — get one
- PATCH /resources/:id — update one
- DELETE /resources/:id — delete one
Best Practices
- Consistent error response format
- Pagination for list endpoints
- Rate limiting middleware
- Request validation on all inputs
- CORS configuration
- Authentication middleware
Pitfalls
- Don't expose internal IDs in public APIs
- Always validate request bodies
- Version your API (v1, v2) from the start
- Don't return sensitive data in error messages
Verification
- All endpoints respond with correct status codes
- Validation rejects malformed input
- Documentation renders correctly
- Auth middleware blocks unauthorized requests
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.
- 4d ago First seen · 65 lines · 41 tokens per session scan A cde21666de86
api-builder is a skill published in the GitHub repository amanning3390/hermeshub (34 stars, last pushed 2mo ago), licensed MIT. It adds 41 tokens to every session and 457 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-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…