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/TestAny-io/testany-agent-skillsWrote 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/testany-io/testany-agent-skills/api-reviewer)<a href="https://agentmods.dev/commands/testany-io/testany-agent-skills/api-reviewer"><img src="https://agentmods.dev/badge/commands/testany-io/testany-agent-skills/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/testany-io/testany-agent-skills/api-reviewer"><img src="https://agentmods.dev/badge/commands/testany-io/testany-agent-skills/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.00012 | $0.00539 |
| Opus 5.5 | $0.00005 | $0.00216 |
| Sonnet 5.5 | $0.00002 | $0.00108 |
| Haiku 4.5 | $0.00001 | $0.00054 |
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 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.
What it actually says
API Reviewer
执行前读取 工作流执行约定：先取证再提问、按实际工具能力回退，并从本次安装位置定位资源。
启动 API Contract 评审流程。作为进入 HLD/LLD/实现前的门禁，检测 PRD→Contract 漂移与契约完整性。 评审先读取 证据、准出与复审规则。P2 不按数量阻断；缺证据不等于产品缺陷；提前门禁失败不取消独立安全检查；完成本轮评审不等于批准工件。
先区分 formal_design 与 bounded_change/amendment；有限增量使用既有有效基线及 Owner 批准，只处理受影响范围，不回补全生命周期文档。详见 ../references/document-amendments.md；完整流程只适用于正式新功能/全量准出。
使用方式
提供文档路径：
$ARGUMENTS
API 审查在研发流程中的位置
PRD → API Writer → API Contract → [API Reviewer] → HLD/LLD/实现
审查框架
采用四道门审查：
- Gate 1 - 基线与覆盖：PRD 基线、范围/所有权、映射覆盖率
- Gate 2 - 协议完整性：各协议必填项检查
- Gate 3 - 漂移与冲突：PRD 漂移、重复造轮子、兼容冲突
- Gate 4 - 兼容性与演进：版本策略、破坏性变更、幂等与错误语义
准出门槛
- P0 = 0（任一 P0 即阻断）
- P1 = 0（任一 P1 即不通过）
- P2 不按数量阻断
必需产出
- 审查报告（含问题清单和证据）
- 准出证书（通过时）
请提供 Contract 路径开始评审。建议同时提供 PRD 和 Index（如为多协议）。
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 · +6 lines f7b1890386ec
- 1mo ago First seen · 43 lines · 12 tokens per session scan A 3844cb442833
api-reviewer is a command published in the GitHub repository TestAny-io/testany-agent-skills (82 stars, last pushed yesterday), licensed MIT. It adds 12 tokens to every session and 539 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-08-30.
Other commands, from other repositories
evaluate-connector
Evaluate a Fivetran connector for correctness, SDK compliance, security, and reliability.
api-review
Review the current code or API against API design principles — identifies violations and suggests improvements.
fec-doc-sync
Sync README, docs, environment variables, scripts, API/routing/component descriptions and deployment instructions from code and project sources of truth.
pn-audit-data
Design or review database schema — normalization, indexing strategy, migration plan, and data model decisions. Surgical command for database design. Use standalone or as part of pn-backend-audit.
dotnet-structure
Analyze and recommend .NET backend solution and folder structure improvements. Checks projects, layers, oversized files, and boundary clarity.
pn-audit-security
OWASP-guided security review — auth posture, input validation, secrets, CORS, JWT, rate limiting. Surgical command for backend security. Use standalone or as part of pn-backend-audit.