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.
git clone --depth 1 https://github.com/Tenon-Net/TenonAdminWrote 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/commands/tenon-net/tenonadmin/api-reviewer)<a href="https://agentmods.dev/commands/tenon-net/tenonadmin/api-reviewer"><img src="https://agentmods.dev/badge/commands/tenon-net/tenonadmin/api-reviewer/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/commands/tenon-net/tenonadmin/api-reviewer"><img src="https://agentmods.dev/badge/commands/tenon-net/tenonadmin/api-reviewer.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.00011 | $0.00499 |
| Opus 5.5 | $0.00004 | $0.00200 |
| Sonnet 5.5 | $0.00002 | $0.00100 |
| Haiku 4.5 | $0.00001 | $0.00050 |
Grade A, and why
api-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 today.
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.
How it starts
The opening of the file, as written. The whole thing — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
<review_focus>
- Identify every changed public API from the diff and inspect all relevant callers and documentation.
- Check history to establish the previous API shape and detect breaking changes.
- Classify each change as breaking (major) or non-breaking (minor/patch), including renamed parameters, changed types, nullability, return values, defaults, and removed behavior.
- Review parameter and return clarity, preconditions/postconditions, naming, parameter order, consistency, and anti-patterns such as boolean flags, many positional parameters, stringly-typed values, and side effects in getters.
- Verify error semantics: possible errors, triggering conditions, representation, messages, and documentation.
- Verify documentation covers parameters, returns, errors, examples, migration guidance, and the recommended version bump. </review_focus>
<severity_and_evidence>
- Cite each concern with
file:lineand the affected public symbol. - For every breaking change, identify affected callers and provide a concrete migration path.
- Distinguish confirmed contract changes from documentation or compatibility risks; support conclusions with history, usage, tests, and docs.
- Stop only after every changed public API has a compatibility assessment and versioning recommendation. </severity_and_evidence>
<output_contract>
API Review
Summary
Overall: [APPROVED / CHANGES NEEDED / MAJOR CONCERNS] Breaking Changes: [NONE / MINOR / MAJOR]
Breaking Changes Found
module.ts:42-functionName()- [description] - Requires major version bump- Migration path: [how callers should update]
API Design Issues
module.ts:156- [issue] - [recommendation]
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.
- today First seen · 47 lines · 11 tokens per session scan A ff3b4a765c71
api-reviewer is a command published in the GitHub repository Tenon-Net/TenonAdmin (41 stars, last pushed 14d ago), licensed Apache-2.0. It adds 11 tokens to every session and 499 once invoked, about $0.0000 per session on Opus 5.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-11-07.
api-reviewer compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| api-reviewerTenon-Net/TenonAdmin | Command | 41 | 14d ago | Apache-2.0 | A | 11 | Claude Code, Codex |
| dotnet-structuremathisk2095/jko-claude-plugins | Command | 3 | 24d ago | MIT | A | 24 | Claude Code |
| check-syncro-apisadvenimus/syncromsp-mcp | Command | 10 | 7d ago | MIT | A | 37 | Claude Code |
| api-reviewoborchers/fractional-cto | Command | 36 | 12d ago | MIT | A | 16 | Claude Code |
| new-middlewaresrnichols/plan-forge | Command | 6 | 2d ago | MIT | A | 22 | GitHub Copilot |
| pn-audit-securityperniemann/pnCore | Command | 0 | 5d ago | MIT | A | 46 | Claude Code, Cursor |
| checklistgithub/spec-kit | Command | 148k | yesterday | MIT | A | 13 | Claude Code |