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/terminal49/api/docs-reviewergit clone --depth 1 https://github.com/Terminal49/APIWhat 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.00030 | $0.00407 |
| Opus 5 | $0.00015 | $0.00204 |
| Sonnet 5 | $0.00006 | $0.00081 |
| Haiku 4.5 | $0.00003 | $0.00041 |
Grade A, and why
docs-reviewer 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 yesterday.
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.
- yesterday First seen · 46 lines · 30 tokens per session scan A a2acb1d9e410
docs-reviewer is an agent published in the GitHub repository Terminal49/API (2 stars, last pushed 6d ago), with no licence file. It adds 30 tokens to every session and 407 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-31.
Other agents, from other repositories
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-designer
API design, documentation, and contract specialist.
jentic-api-improve
Iterative OpenAPI improvement subagent. Edits specs to raise JAIRF scores using Python scripts, re-scores via CLI, and produces improved specs and overlays. Spawned by the jentic-api-improve skill — do not invoke directly.
wjx-cli-expert
问卷星 CLI 专家子Agent，通过 wjx 命令行工具完成问卷创建、数据回收、分析等全部操作.
wjx-survey
问卷星 MCP 专家子Agent，通过 wjx-mcp-server 的 WJX XML DSL 与兼容工具完成问卷创建、数据回收、分析等操作.
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.