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 skills add devcxl/mattpocock-skills-zh --skill implement-specgit clone --depth 1 https://github.com/devcxl/mattpocock-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/skills/devcxl/mattpocock-skills-zh/implement-spec)<a href="https://agentmods.dev/skills/devcxl/mattpocock-skills-zh/implement-spec"><img src="https://agentmods.dev/badge/skills/devcxl/mattpocock-skills-zh/implement-spec.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00011 | $0.00500 |
| Opus 5 | $0.00005 | $0.00250 |
| Sonnet 5 | $0.00002 | $0.00100 |
| Haiku 4.5 | $0.00001 | $0.00050 |
Grade A, and why
implement-spec 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 8d 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
你已被提供一份 spec。该 spec 应关联若干 ticket，用以描述如何实现该 spec。
目标是产出一个 PR，在单个分支上实现整份 spec。
这些 ticket 不是一份步骤清单。它们是一张任务图，彼此之间存在阻塞关系。这意味着始终存在一个前沿（frontier）：可立即被领走的 ticket。
与子智能体之间的通信应保持精简。通信主要通过上下文指针：指向 spec、ticket、研究笔记与历史 commit。无需重复指针已经能触达的信息。
实施者子智能体应尽可能在后台运行，以获得最大并发。
步骤
-
阅读 spec 与 ticket。读到足以理解任务图为止。
-
（可选）使用一个探查子智能体完成 ticket 所需的探查工作：相关的代码库文件或外部文档。确保该探查子智能体能够保存文件：它应把 Markdown 笔记保存在仓库之外、所有后续子智能体都能访问的目录中。这让实施者子智能体可以专心实现，而非探查。
-
创建一个分支，以及一个 draft PR。PR 应标记为"关闭"对应的 spec issue 与 ticket。
-
使用实施者子智能体逐一实现每张 ticket。每个实施者子智能体应在自己的 worktree、自有的分支上工作。
-
一旦某个实施者子智能体完成，使用一个合并子智能体将其工作合并进 PR 分支。
-
如果这改变了可领取 ticket 的前沿，立刻启动更多实施者子智能体去处理新出现的 ticket。这保证了最大并发。
-
所有 ticket 完成后，对 PR 分支运行
/code-review。用一个实施者子智能体一次性修复 code review 提出的全部问题。 -
将 PR 标记为 ready for review。
-
清理所有实施者子智能体的 worktree。
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.
- 8d ago First seen · 35 lines · 11 tokens per session scan A d6b146dd828f
implement-spec is a skill published in the GitHub repository devcxl/mattpocock-skills-zh (318 stars, last pushed 3d ago), licensed MIT. It adds 11 tokens to every session and 500 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 skills, from other repositories
chinese-documentation
A Chinese technical-documentation style guide covering spacing, punctuation, numbers, terminology, and links when Chinese and English appear together.
chinese-code-review
A Chinese-language code-review communication guide with templates and severity levels for review comments.
chinese-commit-conventions
A Chinese-language guide to Conventional Commits, a format for writing consistent Git commit messages, plus related changelog, commit-checking, and commit-helper configuration.
systematic-debugging
A step-by-step method for finding the underlying cause of technical problems before changing code. It covers reading errors, reproducing failures, checking recent changes, and tracing data across system components.
dispatching-parallel-agents
A workflow for assigning separate coding agents to independent tasks that do not share state or depend on one another. Each agent receives a focused scope, constraints, and an expected result.
executing-plans
A procedure for carrying out a written software implementation plan in a separate session, including reviewing the plan, completing its tasks, and checking the results at defined review points.