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 prgit 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/pr)<a href="https://agentmods.dev/skills/devcxl/mattpocock-skills-zh/pr"><img src="https://agentmods.dev/badge/skills/devcxl/mattpocock-skills-zh/pr/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/pr"><img src="https://agentmods.dev/badge/skills/devcxl/mattpocock-skills-zh/pr.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.00011 | $0.01096 |
| Opus 5.5 | $0.00004 | $0.00438 |
| Sonnet 5.5 | $0.00002 | $0.00219 |
| Haiku 4.5 | $0.00001 | $0.00110 |
Grade A, and why
pr 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 27d 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.
This is a copy
100% identical to pr — 88 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 171 lines — stays where its author put it; the contents beside it link to each section on GitHub.
写 PR body 时用这个模板:
## Summary(摘要)
<图表、diff 草图,或树>
## Evidence(证据)
- **Before:** <截图 / 输出 / 失败中的测试运行>
**After:** <截图 / 输出 / 通过了的测试运行>
## Merge Danger(合并风险)
**Door:** <单向门或双向门>
<可选:说明>
**Blast Radius:** <一个词的描述>
<可选:合并的潜在影响>
各章节
跳过所有开场白,行文保持简短。使用 GLOSSARY.md 里用户的领域语言。
Summary(摘要)
挑最小的、能把关键点讲清楚的视图。
- 逻辑或算法用伪代码展示:
on(save)
if content is unchanged
return cached result
write new content
return fresh result
- 运行时控制流用调用树展示:
submitForm
createSession
persistPrompt
launchAgent
navigateToSession
- UI 结构用组件树展示,包含真正重要的状态和模块边界:
<SessionPage> (apps/example/src/routes/session.tsx)
useSessionEvents()
<SessionToolbar>
<RunSkillButton> (packages/ui)
- 文件职责或大范围重构用浅文件树展示:
src/
├── commands/ # 解析用户动作
├── sessions/ # 掌管会话状态
└── transport/ # 发送 API 请求
- 组件交互、控制流或数据流用 Mermaid 展示:
sequenceDiagram
participant User
participant UI
participant Daemon
User->>UI: 选择命令
UI->>Daemon: 发送展开后的提示
Daemon-->>UI: 流式返回结果
- 当重点是"变了什么"、而周围形状已经存在时,用
diff。让 diff 的形状匹配主题。
组件变更:
<SessionPage>
useSessionEvents()
<SessionToolbar>
+ <RunSkillButton />
<SessionTimeline>
+ <SkillResultCard />
文件布局变更:
src/
├── commands/
+│ └── show-me.ts # 展开 slash 命令
├── sessions/
-└── transport.ts
+└── transport/
+ ├── client.ts
+ └── stream.ts
调用树或调用栈变更:
submitForm
createSession
persistPrompt
+ expandSkillMention
launchAgent
- navigateToSession
+ navigateToSession
+ subscribeToEvents
状态或控制流变更:
on(save)
- write content
+ if content is unchanged
+ return cached result
+ write new content
+ invalidate cache
- 当大部分内容都是新的、省略上下文会掩盖归属或顺序、或者用户需要一个可复制的目标形状时,展示完整代码块:
function expandSkill(command: string): string {
const skillName = command.slice(1);
return `use the ${skillName} skill`;
}
指引
把每个视图放在它所支撑的短文字旁边。只保留回答用户当前问题、或解决当前讨论点所需选项所必需的调用、文件、props、状态和边界。
What ships with it
2 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.
- 27d ago Changed · +2 lines 16e51e87be15
- 1mo ago Changed · +2 tokens per session d5fbe4c5cd94
- 1mo ago Changed · +5 lines e91dc57fa0ee
- 1mo ago First seen · 164 lines · 9 tokens per session scan A 9c36a2793b26
pr is a skill published in the GitHub repository devcxl/mattpocock-skills-zh (512 stars, last pushed 4d ago), licensed MIT. It adds 11 tokens to every session and 1,096 once invoked, about $0.0000 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to pr, differing in 88 lines, and is treated as a copy.
Other skills, from other repositories
triage
A process for reviewing issues and outside pull requests through category and status labels. An issue is a recorded problem or request, while a pull request is a proposed code change for review.
pr
A writing guide for creating pull request descriptions, which explain a proposed code change to reviewers. It uses sections for the summary, evidence, merge risk, and the likely area affected by the change.
setup-pre-commit
A setup for Husky pre-commit checks in a JavaScript or TypeScript repository. A pre-commit hook runs automatically before a Git commit and can format staged files, check types, and run tests.
code-review
A code-review skill that compares changes from a chosen commit, branch, tag, or merge-base against the repository’s coding standards and the related issue or specification.
improve-codebase-architecture
A skill that scans a codebase for places where restructuring could make future changes and testing easier, then produces an HTML report for selected improvements.
implement-spec
A coding workflow that implements a written specification through a set of linked tickets. It creates a branch and draft pull request, assigns independent work to separate agents, combines their changes, and prepares the result for review.