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 skills/vitoworleone/claude-code-handbook/testnpx skills add vitoworleone/claude-code-handbook --skill testgit clone --depth 1 https://github.com/vitoworleone/claude-code-handbookWrote 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/skills/vitoworleone/claude-code-handbook/test)<a href="https://agentmods.dev/skills/vitoworleone/claude-code-handbook/test"><img src="https://agentmods.dev/badge/skills/vitoworleone/claude-code-handbook/test.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 | $0.00007 | $0.00348 |
| Opus 5 | $0.00003 | $0.00174 |
| Sonnet 5 | $0.00001 | $0.00070 |
| Haiku 4.5 | $0.00001 | $0.00035 |
Grade A, and why
test 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 5d 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
任务
你需要运行项目的测试套件并分析结果。
步骤
- 检测项目类型，按优先级查找：
pyproject.toml或setup.py→ Python 项目，使用pytestgo.mod→ Go 项目，使用go test ./...package.json→ Node.js 项目，使用npm testCargo.toml→ Rust 项目，使用cargo test
- 运行对应的测试命令，捕获完整输出
- 分析测试结果：
- 如果全部通过：报告通过数量和覆盖率（如可用）
- 如果有失败：区分两种失败原因： a. 代码 bug：断言期望值正确但实际值错误，说明源码有问题 b. 测试 bug：断言期望值本身就不对，或测试设置有误，说明测试需要修复
- 对于每个失败的测试：
- 指出失败位置（文件名、测试名）
- 判断是代码 bug 还是测试 bug
- 给出具体修复建议
- 如果全部通过，检查是否有明显缺失的测试场景：
- 边界值测试
- 错误路径测试
- 空输入/极端值测试
$ARGUMENTS
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago First seen · 39 lines · 7 tokens per session scan A d42cb0a885af
test is a skill published in the GitHub repository vitoworleone/claude-code-handbook (44 stars, last pushed 2d ago), licensed MIT. It adds 7 tokens to every session and 348 once invoked, about $0.0000 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 skills, from other repositories
verify-pr
This skill should be used to run a sandboxed deep verification of a qwen-code PR — "/verify-pr ", "深度验证这个 PR", A/B load-bearing proof against the base build, mock-free harnesses with wire oracles, and targeted gates — producing tmp/pr -verify- /report.md plus a machine-readable verdict. Designed for the token-free CI…
stuck
Diagnose frozen, stuck, or slow Qwen Code sessions on this machine. Scans for problematic processes, high CPU/memory usage, hung subprocesses, and debug logs. Use /stuck or /stuck to focus on a specific process.
e2e-testing
Guide for running end-to-end tests of the Qwen Code CLI, including headless mode, MCP server testing, and API traffic inspection. Use this skill whenever you need to verify CLI behavior with real model calls, reproduce user-reported bugs end-to-end, test MCP tool integrations, or inspect raw API request/response…
structured-debugging
Hypothesis-driven debugging methodology for hard bugs. Use this skill whenever you're investigating non-trivial bugs, unexpected behavior, flaky tests, or tracing issues through complex systems. Activate proactively when debugging requires more than a quick glance — especially when the first attempt at a fix didn't…
batch
Execute batch operations on multiple files in parallel. Automatically discovers files, splits into chunks, and processes with parallel worker agents. Use /batch followed by operation and file pattern.
desktop-brand-builder
Generate a branded Qwen Code desktop package from the Tauri desktop shell using a minimal brandId and logo. Use when the user wants a custom, white-label, or rebranded desktop client, installer, DMG/EXE/AppImage/deb, or one-click brand build on top of packages/desktop-shell.