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 a1f/agent-templates --skill to-issuesgit clone --depth 1 https://github.com/a1f/agent-templatesWrote 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/a1f/agent-templates/to-issues)<a href="https://agentmods.dev/skills/a1f/agent-templates/to-issues"><img src="https://agentmods.dev/badge/skills/a1f/agent-templates/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/a1f/agent-templates/to-issues"><img src="https://agentmods.dev/badge/skills/a1f/agent-templates/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.00035 | $0.01066 |
| Opus 5.5 | $0.00014 | $0.00426 |
| Sonnet 5.5 | $0.00007 | $0.00213 |
| Haiku 4.5 | $0.00003 | $0.00107 |
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 2mo 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 — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
To Issues
Break a PRD issue into vertical, tracer-bullet slices — each a narrow but COMPLETE path through every layer it touches (schema, API, UI, tests), demoable on its own — recorded as one growing table inside the same issue, never fanned out. Prefer many thin slices over a few thick ones; order them thinnest-first.
/to-issues [--issue=N]
1. Find the issue and read it
2. Draft slices + parallelization
3. Discuss and refine (gate)
4. Append the plan to the SAME issue
Phase 1 — Find the issue
Use --issue=N if given. Otherwise scan the conversation for the last
PRD published: ... (issue #N) line; if there's none, ask. If you auto-detected
it, confirm the number with the user. Read the body; use the codebase's own
vocabulary; respect ADRs.
Phase 2 — Draft slices
Each slice carries a Demoable as line (how you'd demo or verify it — if you
can't write one, it isn't end-to-end), a Mode (AFK = an agent runs it alone;
HITL = needs the user: design taste, UX, a judgment call), a Size (S/M/L,
a rough feel — real line counts come in pr-breakdown, which budgets each PR at ~35
counted lines, so an L slice means many PRs, never one big one), and Blocked by.
## Build plan — vertical slices
| # | What | Demoable as | Mode | Size | Blocked by |
|---|------|-------------|------|------|------------|
| 1 | ... | ... | AFK | M | — |
### Parallelization
| Wave | Runs together | Notes |
|------|---------------|-------|
| 0 | 1 | foundation |
| 1 | 2 + 3 | independent |
**Critical path:** 1 → 2 → ...
Waves are a topological grouping of Blocked by: same-wave slices share no
blocking relationship. If the work has no real slices (e.g. one tiny change),
say so — and still write the ## Build plan — vertical slices heading with a
single line, No slicing — single PR, so the next phase proceeds.
Phase 3 — Discuss (gate)
Present the slices as a numbered list, then ask the user:
- Is the granularity right — too coarse, too fine?
- Are the dependencies correct?
- Merge or split any (e.g. an
Lslice worth splitting)? - Are the HITL/AFK calls right?
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.
- 2mo ago First seen · 100 lines · 35 tokens per session scan A b16791378dc9
to-issues is a skill published in the GitHub repository a1f/agent-templates (2 stars, last pushed 2mo ago), licensed MIT. It adds 35 tokens to every session and 1,066 once invoked, about $0.0001 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
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…