Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/TestAny-io/testany-agent-skillsnpx agentmods add commands/testany-io/testany-agent-skills/test-reviewerWrote 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/test-reviewer)<a href="https://agentmods.dev/commands/testany-io/testany-agent-skills/test-reviewer"><img src="https://agentmods.dev/badge/commands/testany-io/testany-agent-skills/test-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/test-reviewer"><img src="https://agentmods.dev/badge/commands/testany-io/testany-agent-skills/test-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.00029 | $0.00535 |
| Opus 5 | $0.00015 | $0.00267 |
| Sonnet 5 | $0.00006 | $0.00107 |
| Haiku 4.5 | $0.00003 | $0.00053 |
Grade A, and why
test-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 10d 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
Test Reviewer
启动测试门禁评审流程。检查独立测试包是否完整、可执行、与上游基线一致；在发布前模式下，同时检查执行证据与残余风险，并在通过时给出文档下游与 Testany 自动化下游建议。
使用方式
提供测试规格、测试策略，以及可选的执行摘要/缺陷清单：
$ARGUMENTS
在研发流程中的位置
Test Spec → [Test Reviewer] → 测试准出 → Runbook / Testany automation landing
审查框架
采用四道门审查：
- Gate 1 - 基线与追溯：版本、范围、覆盖映射
- Gate 2 - 覆盖与漂移：覆盖率口径、主流程、异常、边界、系统集成/兼容、非功能
- Gate 3 - 可执行性与证据设计：数据、环境、依赖、断言、分组
- Gate 4 - 执行证据与残余风险：执行结果、缺陷、豁免、发布前证据
准出门槛
- P0 = 0
- P1 = 0
- P2 ≤ 2
必需产出
- 审查报告
- 准出证书（通过时）
- 下游 handoff 建议（通过时）
强制脚本校验
在人工评审前必须先执行：
python3 plugins/testany-eng/scripts/trace_lint.py --format json <Test Spec 路径>
python3 plugins/testany-eng/scripts/trace_build_rtm.py --format json <PRD 路径> <Test Strategy 路径> <Test Spec 路径>
trace-build-rtm 的 Requirement / Risk / Must-not-regress / External Behavior 矩阵，是 Gate 1 / Gate 2 的主证据来源。
请提供 Test Spec 路径开始评审。若是发布前门禁，务必同时提供执行摘要或缺陷清单。
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.
- 10d ago First seen · 55 lines · 29 tokens per session scan A b4db494a7814
test-reviewer is a command published in the GitHub repository TestAny-io/testany-agent-skills (81 stars, last pushed 2d ago), licensed MIT. It adds 29 tokens to every session and 535 once invoked, about $0.0001 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 commands, from other repositories
prototype
You are building a proof-of-concept for the current Grainulator sprint. Read CLAUDE.md for sprint context and claims.json for existing research claims.
verify
Run repository verification using the verification-loop skill.
qa-changes
This skill should be used when the user asks to "QA a pull request", "test PR changes", "verify a PR works", "functionally test changes", or when an automated workflow triggers QA validation of code changes. Provides a structured methodology for setting up the environment, exercising changed behavior, and reporting…
test-coverage
Analyze test coverage and identify the highest-value gaps to fill.
tdd
A command that follows test-driven development (TDD), a method where you write tests before the code they check. It moves through writing a failing test, adding the smallest implementation, and then improving the code.
check-dev
Type-check a Z specification with fuzz.