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 agentmods add skills/voidtechnology/voidtech-claude-plugins/prepare-issuenpx skills add VoidTechnology/voidtech-claude-plugins --skill prepare-issuegit clone --depth 1 https://github.com/VoidTechnology/voidtech-claude-pluginsWhat 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 | $0.00037 | $0.01788 |
| Opus 5 | $0.00018 | $0.00894 |
| Sonnet 5 | $0.00007 | $0.00358 |
| Haiku 4.5 | $0.00004 | $0.00179 |
Grade A, and why
prepare-issue 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 yesterday.
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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vendored from mattpocock/skills · MIT © 2026 Matt Pocock · upstream 6eeb81b · 已汉化并完成 VoidTech 插件内自包含适配。LICENSE 见 ../_vendor-licenses/mattpocock-LICENSE
Issue 与 PR 整理
按照一套明确的分类和状态规则整理项目中的 issue。
开始前读取 Issue 跟踪器适配契约，据此识别平台、认证、标签映射和外部贡献者。如果适配器支持 PR，整理范围也包括 PR：一个 PR 可以视为附带代码的 issue——使用相同的分类、状态和流转规则，差异会在下文单独说明。裸 #42 优先在当前仓库中解析；无法唯一判断是 issue 还是 PR 时查询两者，而不是猜测。
整理期间发布到 issue 追踪器的每一条评论或 issue 都必须以这段免责声明开头：
> *This was generated by AI during triage.*
参考文档
- AGENT-BRIEF.md — 如何写出长期有效的 agent 实现说明
- OUT-OF-SCOPE.md —
.out-of-scope/知识库如何运作
角色
两个**category（分类）**角色：
bug— 某处坏了enhancement— 新功能或改进
五个**state（状态）**角色：
needs-triage— 维护者需要评估needs-info— 等待报告者补充更多信息ready-for-agent— 信息完整，可供无人值守 agent 直接实现ready-for-human— 需要人工实现wontfix— 不会处理
对于 PR，这些状态描述的是其代码处理进度：ready-for-agent 表示已有实现说明，agent 可以继续处理该 diff；ready-for-human 表示代码已准备好由人工合并。
每个已整理的 issue 应当恰好具有一个分类标签和一个状态标签。如果状态标签相互冲突，先指出冲突并询问维护者，再执行其他操作。
这些是规范的角色名——issue 追踪器中实际使用的标签字符串可能不同。按适配契约查询、确认并在本次会话中复用映射，不依赖仓库外配置。
状态流转：一个未打标签的 issue 通常先进入 needs-triage；从那里它移动到 needs-info、ready-for-agent、ready-for-human 或 wontfix。needs-info 在报告者回复后回到 needs-triage。维护者可以随时覆盖——把看起来异常的流转标出来并在继续前询问。
调用
维护者调用 /voidtech-engineering:prepare-issue 并用自然语言描述他们想要什么。解读该请求并采取行动。示例：
- "Show me anything that needs my attention"
- "Let's look at #42"（issue 或 PR）
- "Move #42 to ready-for-agent"
- "What's ready for agents to pick up?"
展示需要关注的内容
查询 issue 追踪器并分成以下三组，组内按时间从旧到新排列：
- Unlabeled — 从未整理过。
needs-triage— 评估进行中。needs-info且报告者在上次整理备注后有新活动 — 需要重新评估。
如果范围包含 PR，也把外部 PR 放入这些分组，并用 [PR] 或 [issue] 标记。自动查询只列出外部贡献者的 PR，协作者正在处理的 PR 不需要重复整理。用户明确指定的 PR 始终处理，不受此过滤限制。
为每个条目展示计数和一行摘要。让维护者来挑选。
整理特定 issue 或 PR
- 收集上下文。 阅读完整的 issue 或 PR，包括正文、评论、标签、作者和日期；PR 还要读取 diff。整理已有备注，避免重复询问已经解决的问题。结合项目业务词汇表、相关代码和 ADR 做两项检查：(a) 是否已经实现：按业务概念搜索现有行为，并说明查过哪些位置；若已实现，按步骤 5 的“已实现”分支处理。(b) 是否曾被拒绝：读取
.out-of-scope/*.md，列出与当前请求相似的记录。
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.
- yesterday First seen · 114 lines · 37 tokens per session scan A c86720c4a041
prepare-issue is a skill published in the GitHub repository VoidTechnology/voidtech-claude-plugins (2 stars, last pushed 28d ago), licensed Apache-2.0. It adds 37 tokens to every session and 1,788 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…