Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/VoidTechnology/voidtech-claude-pluginsnpx agentmods add skills/voidtechnology/voidtech-claude-plugins/to-issuesWrote 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/voidtechnology/voidtech-claude-plugins/to-issues)<a href="https://agentmods.dev/skills/voidtechnology/voidtech-claude-plugins/to-issues"><img src="https://agentmods.dev/badge/skills/voidtechnology/voidtech-claude-plugins/to-issues/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/voidtechnology/voidtech-claude-plugins/to-issues"><img src="https://agentmods.dev/badge/skills/voidtechnology/voidtech-claude-plugins/to-issues.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.00043 | $0.01131 |
| Opus 5.5 | $0.00017 | $0.00452 |
| Sonnet 5.5 | $0.00009 | $0.00226 |
| Haiku 4.5 | $0.00004 | $0.00113 |
Grade A, and why
to-issues 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 1mo 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
Vendored from mattpocock/skills · MIT © 2026 Matt Pocock · upstream 6eeb81b · 已汉化并完成 VoidTech 插件内自包含适配。LICENSE 见 ../_vendor-licenses/mattpocock-LICENSE
转为 Issues
把计划拆成端到端垂直切片，每个切片都能独立认领和验证。
开始前读取 Issue 跟踪器适配契约，据此识别平台、认证和标签映射；不要求任何预先安装的初始化技能。
流程
1. 收集上下文
从对话上下文里已有的内容着手。如果用户传入一个 issue 引用（issue 编号、URL 或路径）作为参数，从 issue 跟踪器取回它，读全文及评论。
2. 探查代码库（可选）
如果你还没探查过代码库，就去探查，以理解代码当前状态。issue 标题与描述应使用项目业务词汇表的词汇，并尊重你所改动区域内的 ADR。
检查是否需要先做小范围重构，以降低后续实现的复杂度。此类重构必须与目标改动直接相关，并能独立验证。
3. 起草垂直切片
把计划拆成小而完整的垂直切片。每个 issue 都要端到端覆盖必要的集成层，而不是只处理某一层。
- 每个切片交付一条窄而完整的路径，穿过每一层（schema、API、UI、测试）
- 一片完成的切片本身可演示或可验证
- 必要的前置重构应拆成更早完成的独立 issue
4. 向用户求证
把建议的拆分以编号列表呈现。对每个切片，展示：
- 标题：简短的描述性名称
- 前置依赖：哪些其他切片（若有）必须先完成
- 覆盖的用户故事：这片切片处理了哪些用户故事（若源材料含有用户故事）
向用户提问：
- 每个 issue 的大小是否合适？（太大 / 太小）
- 依赖关系正确吗？
- 是否有切片应当合并或进一步拆分？
迭代直到用户批准这套拆分。
5. 把 issue 发布到 issue 跟踪器
对每个获批切片，向 issue 跟踪器发布一个新 issue。使用下方模板。默认把这些 issue 写得足够完整，让无人值守 agent 可以直接实现；除非另有指示，发布时使用 category enhancement 与 state ready-for-agent 对应的实际标签。
发布前可按 voidtech-core:text-naturalizer 的规则轻量自审标题、目标描述和背景说明，去掉模板腔和抽象话。若 Skill 工具可用，调用 voidtech-core:text-naturalizer 处理这些段落；若不可用，按本条规则自行审阅并改写，不从当前插件目录猜测 Core 的安装路径。不要改写验收标准、前置依赖、标签、issue 结构、代码片段、接口名、字段名或业务术语；这些内容的可验证性和精确性优先于文案自然度。
按依赖顺序（先发布阻塞方）发布 issue，这样你才能在 "Blocked by" 字段中引用真实的 issue 标识符。
指向 issue 跟踪器上父 issue 的引用（若源是一个既有 issue，否则省略本节）。
目标
对这片垂直切片的简洁描述。描述端到端的行为，而非逐层的实现。
避免具体的文件路径或代码片段，因为它们很快就会过时。例外：如果原型中的片段能更准确地表达某项决策（状态机、reducer、schema、类型形态），可以把它放在这里，并注明来源。只保留表达决策所需的部分，不要附上完整演示。
验收标准
- Criterion 1
- Criterion 2
- Criterion 3
前置依赖
- 指向阻塞工单的引用（若有）
没有依赖时写“无，可立即开始”。
不要关闭或修改任何父 issue。若跟踪器不可用，按适配契约输出完整草稿；草稿生成完成后才算本次任务达到可交付状态。
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.
- 1mo ago First seen · 88 lines · 43 tokens per session scan A dc7a45d209d4
to-issues is a skill published in the GitHub repository VoidTechnology/voidtech-claude-plugins (2 stars, last pushed 5d ago), licensed Apache-2.0. It adds 43 tokens to every session and 1,131 once invoked, about $0.0002 per session on Opus 5.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
story-readiness
Is a story implementation-ready? Checks clear acceptance criteria, open questions, ADR refs. READY/NEEDS WORK/BLOCKED/NOT ASSESSED.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…