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 commands/shenjingnan/xiaozhi-client/increase-coveragegit clone --depth 1 https://github.com/shenjingnan/xiaozhi-clientWrote 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/shenjingnan/xiaozhi-client/increase-coverage)<a href="https://agentmods.dev/commands/shenjingnan/xiaozhi-client/increase-coverage"><img src="https://agentmods.dev/badge/commands/shenjingnan/xiaozhi-client/increase-coverage.svg" alt="Measured on agentmods" 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.00013 | $0.00365 |
| Opus 5 | $0.00006 | $0.00182 |
| Sonnet 5 | $0.00003 | $0.00073 |
| Haiku 4.5 | $0.00001 | $0.00036 |
Grade A, and why
increase-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 6d 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
上下文
- 分叉点 commit: !
git merge-base main HEAD - 当前分支改动文件列表: !
git --no-pager diff --name-only main...HEAD - 当前分支改动内容: !
git --no-pager diff main...HEAD - 当前覆盖率基线: !
pnpm run test:coverage 2>&1
你的任务
根据上述信息，为当前分支的改动补充测试覆盖：
- 分析当前分支改动，识别变更的核心逻辑文件（排除配置文件、类型定义等非逻辑文件）
- 查看当前覆盖率报告，记录基线数据
- 分析哪些核心逻辑缺少测试覆盖，重点关注：
- 新增的函数和方法
- 修改后的条件分支
- 边界场景和异常处理
- 为缺少覆盖的逻辑补充测试用例，测试文件放在
src/__tests__/目录下 - 运行
pnpm run test确保全部测试通过，如有失败则修复 - 运行
pnpm run test:coverage获取更新后的覆盖率 - 输出总结：覆盖率从 X% 提升到 Y%，新增了哪些测试用例
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.
- 6d ago First seen · 27 lines · 13 tokens per session scan A f5ba541cf645
increase-coverage is a command published in the GitHub repository shenjingnan/xiaozhi-client (338 stars, last pushed 2d ago), licensed MIT. It adds 13 tokens to every session and 365 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
write-tests
Generate comprehensive test coverage for existing code.
test-tdd
Run when user calls /test-tdd. Scans modified files, locates their corresponding unit/integration test suites, and runs them.
kill-mutants
Analyze surviving mutants from a mutation testing run and write targeted unit tests to kill them. Re-runs mutations to confirm kills.
test
Generate comprehensive tests.
pr-enhance
Command "pr-enhance" from ruvnet/ruflo, covering pr-enhance, usage, options, examples and enhance pr.
unit-test
Write / run the unit tests for the feature. (AIDLC Unit Test phase) Usage: /unit-test.