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/zhukunpenglinyutong/ai-maxWrote 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/zhukunpenglinyutong/ai-max/test-coverage)<a href="https://agentmods.dev/commands/zhukunpenglinyutong/ai-max/test-coverage"><img src="https://agentmods.dev/badge/commands/zhukunpenglinyutong/ai-max/test-coverage/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/zhukunpenglinyutong/ai-max/test-coverage"><img src="https://agentmods.dev/badge/commands/zhukunpenglinyutong/ai-max/test-coverage.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.00000 | $0.00200 |
| Opus 5 | $0.00000 | $0.00100 |
| Sonnet 5 | $0.00000 | $0.00040 |
| Haiku 4.5 | $0.00000 | $0.00020 |
Grade A, and why
test-coverage 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
测试覆盖率
分析测试覆盖率并生成缺失的测试：
-
运行带覆盖率的测试：npm test --coverage 或 pnpm test --coverage
-
分析覆盖率报告（coverage/coverage-summary.json）
-
识别低于 80% 覆盖率阈值的文件
-
对于每个覆盖不足的文件：
- 分析未测试的代码路径
- 为函数生成单元测试
- 为 API 生成集成测试
- 为关键流程生成 E2E 测试
-
验证新测试通过
-
显示覆盖率变化前后的指标
-
确保项目达到 80% 以上的总体覆盖率
重点关注：
- 正常路径场景
- 错误处理
- 边界情况（null、undefined、空值）
- 边界条件
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 · 28 lines · 0 tokens per session scan A e8aa7e58be15
test-coverage is a command published in the GitHub repository zhukunpenglinyutong/ai-max (335 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 200 tokens. 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.