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 agents/viksant/vibe-coding-tools-content/api-documentation-generatorgit clone --depth 1 https://github.com/viksant/vibe-coding-tools-contentWhat 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.00007 | $0.03105 |
| Opus 5 | $0.00003 | $0.01553 |
| Sonnet 5 | $0.00001 | $0.00621 |
| Haiku 4.5 | $0.00001 | $0.00311 |
Grade A, and why
api-documentation-generator 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 2d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 2d ago First seen · 305 lines · 7 tokens per session scan A 36b9f47dd533
api-documentation-generator is an agent published in the GitHub repository viksant/vibe-coding-tools-content (44 stars, last pushed 2mo ago), with no licence file. It adds 7 tokens to every session and 3,105 once invoked, about $0.0000 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 agents, from other repositories
api-designer
API design, documentation, and contract specialist.
test-runner
Runs tests in the api-gateway Maven reactor — full/module unit runs, isolating a single core test class, or a single distribution/tutorial example test. Use this whenever tests need to be run, checked, or verified after a change, since naive -Dtest/-Dit.test invocations silently run (or skip) the wrong thing in this…
api-architect
Use this agent PROACTIVELY when designing API architectures, defining contracts, planning integration patterns, making decisions about REST vs GraphQL, establishing authentication strategies, designing rate limiting systems, planning API versioning approaches, or creating OpenAPI specifications. Invoke for any API…
backend-system-architect
Backend architect: REST/GraphQL APIs, database schemas, microservice boundaries, distributed systems, clean architecture.
api-documenter
Create OpenAPI/Swagger specs, generate SDKs, and write developer documentation. Handles versioning, examples, and interactive docs. Use proactively for API documentation or client library generation.
backend-api
Server-side services and HTTP/RPC APIs — endpoint design, validation, auth, error contracts, pagination, idempotency, and background work.