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/vinvcn/addyosmani-agent-skills-zhWrote 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/vinvcn/addyosmani-agent-skills-zh/build)<a href="https://agentmods.dev/commands/vinvcn/addyosmani-agent-skills-zh/build"><img src="https://agentmods.dev/badge/commands/vinvcn/addyosmani-agent-skills-zh/build/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/vinvcn/addyosmani-agent-skills-zh/build"><img src="https://agentmods.dev/badge/commands/vinvcn/addyosmani-agent-skills-zh/build.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.00014 | $0.00171 |
| Opus 5 | $0.00007 | $0.00086 |
| Sonnet 5 | $0.00003 | $0.00034 |
| Haiku 4.5 | $0.00001 | $0.00017 |
Grade A, and why
build 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 11d 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
同时调用 agent-skills:incremental-implementation skill 和 agent-skills:test-driven-development。
从 plan 中选择下一个 pending task。对每个 task：
- 阅读该 task 的 acceptance criteria
- 加载相关上下文（现有代码、patterns、types）
- 为预期行为编写一个失败测试（RED）
- 实现能让测试通过的最小代码（GREEN）
- 运行完整 test suite 检查 regressions
- 运行 build 验证 compilation
- 使用描述性 message 提交
- 标记该 task 完成并进入下一个
如果任何步骤失败，遵循 agent-skills:debugging-and-error-recovery skill。
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.
- 11d ago First seen · 19 lines · 14 tokens per session scan A 52029f337eeb
build is a command published in the GitHub repository vinvcn/addyosmani-agent-skills-zh (31 stars, last pushed 4mo ago), licensed MIT. It adds 14 tokens to every session and 171 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
build
Implement tasks incrementally — build, test, verify, commit. Add "auto" to run the whole plan in one approved pass.
build
Implement tasks incrementally — build, test, verify, commit. Add "auto" to run the whole plan in one approved pass.
ship
Run the pre-launch checklist via parallel fan-out to specialist personas, then synthesize a go/no-go decision.
test
Run TDD workflow — write failing tests, implement, verify. For bugs, use the Prove-It pattern.
ship
Run the pre-launch checklist via parallel fan-out to specialist personas, then synthesize a go/no-go decision.
test
Run TDD workflow — write failing tests, implement, verify. For bugs, use the Prove-It pattern.