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 to-ticketsgit 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/to-tickets)<a href="https://agentmods.dev/skills/devcxl/mattpocock-skills-zh/to-tickets"><img src="https://agentmods.dev/badge/skills/devcxl/mattpocock-skills-zh/to-tickets/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/to-tickets"><img src="https://agentmods.dev/badge/skills/devcxl/mattpocock-skills-zh/to-tickets.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.00071 | $0.01452 |
| Opus 5 | $0.00036 | $0.00726 |
| Sonnet 5 | $0.00014 | $0.00290 |
| Haiku 4.5 | $0.00007 | $0.00145 |
Grade A, and why
to-tickets 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 — 106 lines — stays where its author put it; the contents beside it link to each section on GitHub.
拆分为 Ticket
将计划、规范或对话拆分为一组 ticket——tracer-bullet 垂直切片，每个都声明阻塞它的其他 ticket。
Issue 跟踪器和分类标签词汇表应已提供给你——如果没有，请告诉用户运行 /setup-matt-pocock-skills。
流程
1. 收集上下文
从对话上下文中已有的内容开始。如果用户传入引用（规范路径、Issue 编号或 URL）作为参数，获取它并读取其完整正文和评论。
2. 探索代码库（可选）
如果你尚未探索代码库，请先了解代码的当前状态。Ticket 标题和描述应使用项目的领域术语表词汇，并尊重你正在接触的区域的 ADR。
寻找预重构代码的机会，使实现更简单。"让改动变得容易，然后再做容易的改动。"
3. 起草垂直切片
将工作拆分为 tracer bullet ticket。
- 每个切片在每个层面（schema、API、UI、测试）走一条狭窄但完整的通路——是垂直的，而不是某一层的水平切片
- 一个完成的切片本身是可演示或可验证的
- 每个切片大小适合单个全新的上下文窗口
- 任何预重构应首先完成
为每个 ticket 指定其阻塞边——必须先完成才能开始的其他 ticket。没有阻塞项的 ticket 可以立即开始。
大范围重构是垂直切片的例外。 大范围重构 是一种机械性变更（重命名列、更改共享符号类型），其影响范围波及整个代码库，一次编辑会同时破坏数千个调用点，导致没有任何垂直切片能保持绿色。不要硬塞进 tracer bullet；按 扩展-收缩（expand–contract） 序列化。首先扩展：在旧形式旁边添加新形式，确保任何东西都没坏。然后按影响范围大小分批迁移调用点（按包、按目录），每批一个 ticket 被扩展阻塞，由于旧形式仍存在，CI 在批次之间保持绿色。最后收缩：所有调用者迁移完后删除旧形式，作为一个被每个迁移批次阻塞的 ticket。当批次本身也无法单独保持绿色时，保留这个序列，但让它们共享一个集成分支，所有批次都阻塞一个最终的"集成并验证" ticket——绿色只在那里承诺。
4. 征求用户意见
以编号列表的形式展示提议的拆解方案。对每个 ticket，展示：
- 标题：简短描述性名称
- 被以下阻塞：哪些其他 ticket（如果有）必须先完成
- 交付内容：此 ticket 让哪个端到端行为生效
询问用户：
- 粒度是否合适？（太粗 / 太细）
- 阻塞边是否正确：每个 ticket 是否只依赖真正制约它的 ticket？
- 是否需要合并或进一步拆分某些 ticket？
迭代直到用户批准拆解方案。
5. 将 ticket 发布到已配置的跟踪器
发布已批准的 ticket。发布方式取决于 /setup-matt-pocock-skills 配置的跟踪器——ticket 本身相同，只有阻塞边的形式不同：
- 本地文件 → 在
.scratch/<feature-slug>/issues/<NN>-<slug>.md下为每个 ticket 写入一个文件，按依赖顺序从01开始编号（阻塞项优先）。每个文件的 "Blocked by" 列出它依赖的编号/标题。使用下面的 per-ticket 文件模板：一个 ticket 一个文件，绝不合并为一个文件。 - 真实 issue 跟踪器（GitHub、Linear……） → 按依赖顺序每个 ticket 发布一个 issue（阻塞项优先），这样每个 ticket 的阻塞边可以引用真实标识符。在平台支持原生阻塞/子 issue 关系的地方使用；否则把每个 ticket 的 "Blocked by" 设为阻塞它的 issue。除非另有指示，应用
ready-for-agent分类标签——这些 ticket 本身就具备 agent 可抓取性。
按前沿推进：任意一个阻塞项已全部完成的 ticket。对纯粹的线性链来说就是从上到下。
不要关闭或修改任何父 issue。
: <Ticket 标题>
What to build: 此 ticket 让哪个端到端行为生效——从用户视角出发，而不是逐层的实现清单。
Blocked by: 制约此 ticket 的其他 ticket 的编号/标题，或 "None (can start immediately)"。
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.
- 12d ago First seen · 106 lines · 71 tokens per session scan A 542c6ddc9d72
to-tickets is a skill published in the GitHub repository devcxl/mattpocock-skills-zh (340 stars, last pushed 7d ago), licensed MIT. It adds 71 tokens to every session and 1,452 once invoked, about $0.0004 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
openspec-bulk-archive-change
Archive multiple completed changes at once. Use when archiving several parallel changes.
requirement-delivery
A workflow for turning a new software request into a small, working deliverable. It clarifies acceptance criteria, identifies boundaries, breaks work into demonstrable parts, and looks for existing code or tools to reuse.
loop-orchestrator
Operate a fleet of durable agent loops under .loop/ — schedule which loop runs next, assign agents to roles (maker vs checker), enforce promotion gates from propose-only to write access, allocate budgets, detect stalled or dead loops, and roll up fleet status into one report. Use when asked to "run the loops"…
creator-productivity
Task management and workspace memory for creative work sessions. Manages a TASKS.md file for project tracking, a two-tier memory system (CREATOR.md + creator-memory/), and a daily sprint structure. Use when organizing creative projects, tracking content tasks, or starting a focused work session.
product-management-expert
Product management expertise for strategy, discovery, prioritization, roadmaps, PRDs, metrics, and stakeholder communication. Use when defining what to build, why, and how to measure success.
todo-discipline
Use when starting any complex task (3+ steps) or before declaring work complete. Enforces todo/task state to match reality — merge updates + read verification. Prevents false completion.