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 setup-matt-pocock-skillsgit 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/setup-matt-pocock-skills)<a href="https://agentmods.dev/skills/devcxl/mattpocock-skills-zh/setup-matt-pocock-skills"><img src="https://agentmods.dev/badge/skills/devcxl/mattpocock-skills-zh/setup-matt-pocock-skills/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/skills/devcxl/mattpocock-skills-zh/setup-matt-pocock-skills"><img src="https://agentmods.dev/badge/skills/devcxl/mattpocock-skills-zh/setup-matt-pocock-skills.svg" alt="Reviewed on agentmods" width="80" 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.00043 | $0.01852 |
| Opus 5 | $0.00022 | $0.00926 |
| Sonnet 5 | $0.00009 | $0.00370 |
| Haiku 4.5 | $0.00004 | $0.00185 |
Grade A, and why
setup-matt-pocock-skills 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 12d 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.
How it starts
The opening of the file, as written. The whole thing — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
设置 Matt Pocock 技能
搭建工程技能所依赖的逐仓库配置：
- Issue 跟踪器 — issue 放在哪里（默认 GitHub；本地 markdown 也开箱即用）
- 分类标签 — 五个规范分类角色所用的标签字符串
- 领域文档 —
CONTEXT.md和 ADR 放在哪里，以及读取它们的消费规则
这是一个提示驱动的技能，不是确定性的脚本。探索、呈现你的发现、与用户确认，然后写入。
流程
1. 探索
查看当前仓库，了解它的起始状态。读一切存在的东西；不要假设：
git remote -v和.git/config— 这是 GitHub 仓库吗？是哪一个？- 仓库根目录的
AGENTS.md和CLAUDE.md— 存在吗？里面是否已有## Agent skills章节？ - 仓库根目录的
CONTEXT.md和CONTEXT-MAP.md docs/adr/和任何src/*/docs/adr/目录docs/agents/— 这个技能之前的产出是否已存在？.scratch/— 表明本地 markdown issue 跟踪器约定已在使用的迹象triage技能是否已安装？（与这个技能文件夹并列的triage技能文件夹，或你的可用技能中有triage。）这决定 B 节是否执行。- Monorepo 信号 — 有
pnpm-workspace.yaml、package.json里有workspaces字段，或有带自己的src/的packages/*。只在真正大的多包仓库里出现；没有它们就是单上下文，而几乎所有仓库都是单上下文。
2. 呈现发现并询问
总结哪些存在、哪些缺失。然后按顺序过各节——一节、一个回答，然后下一节。
每节先用推荐答案开头，让用户一个字就能接受。只有在选择确实分叉时才给一行解释；当探索已经解决了该节时就整节跳过（没装 triage 时跳过 B 节，没有 monorepo 时跳过 C 节）。
A 节 — Issue 跟踪器。
解释：这个仓库的 "issue tracker" 就是 issue 存放的地方。
to-tickets、triage、to-spec等技能会读写它——它们需要知道该调用gh issue create、在.scratch/下写 markdown 文件，还是遵循你描述的其他工作流。选一个你实际为本仓库跟踪工作的位置。
默认姿态：这些技能是为 GitHub 设计的。如果 git remote 指向 GitHub，就提议 GitHub。如果 git remote 指向 GitLab（gitlab.com 或自托管主机），就提议 GitLab。否则（或用户偏好），提供：
- GitHub — issue 存在仓库的 GitHub Issues 里（使用
ghCLI） - GitLab — issue 存在仓库的 GitLab Issues 里（使用
glabCLI） - 本地 markdown — issue 作为
.scratch/<feature>/下的文件存在本仓库中（适合单人项目或没有 remote 的仓库） - 其他（Jira、Linear 等）— 让用户用一段话描述工作流；技能会把它记录为自由文本
把选择记录在 docs/agents/issue-tracker.md。GitHub 和 GitLab 模板带有"PRs as a request surface"（把 PR 当作请求入口）标志，默认关闭——保持关闭，不要提起它；想把外部 PR 放进分类队列的用户可以稍后在文件里打开这个标志。
B 节 — 分类标签词汇。 如果 triage 技能未安装（探索已告诉你），整节跳过——未安装的技能不需要标签。
如果已安装，只问一个问题：
你想保留默认的分类标签吗？（推荐：是）
默认值就是五个规范角色，每个标签字符串等于其角色名：needs-triage、needs-info、ready-for-agent、ready-for-human、wontfix。选是，就原样写入。只有当用户说不——通常是因为他们的跟踪器已经用了别的名字（比如用 bug:triage 表示 needs-triage）——才收集覆盖项，这样 triage 会应用已有标签而不是创建重复的。
What ships with it
6 files 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.
- 12d ago First seen · 117 lines · 43 tokens per session scan A 0a56bd86f9ea
setup-matt-pocock-skills is a skill published in the GitHub repository devcxl/mattpocock-skills-zh (343 stars, last pushed 7d ago), licensed MIT. It adds 43 tokens to every session and 1,852 once invoked, about $0.0002 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.