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 breakdowngit 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/breakdown)<a href="https://agentmods.dev/skills/a1f/agent-templates/breakdown"><img src="https://agentmods.dev/badge/skills/a1f/agent-templates/breakdown/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/breakdown"><img src="https://agentmods.dev/badge/skills/a1f/agent-templates/breakdown.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.00044 | $0.00571 |
| Opus 5.5 | $0.00018 | $0.00228 |
| Sonnet 5.5 | $0.00009 | $0.00114 |
| Haiku 4.5 | $0.00004 | $0.00057 |
Grade A, and why
breakdown 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.
What it actually says
Breakdown
Run the full planning pipeline — PRD → slices → PR breakdown — into one
growing GitHub issue, pausing at each gate. Composes to-prd, to-issues, and
pr-breakdown, each invoked directly.
/breakdown [description or context] [--title="..."] [--label=Plan]
Phase 1: to-prd → creates the issue (gates: clarify, approve)
Phase 2: to-issues → appends slices (gate: discuss)
Phase 3: pr-breakdown → appends PR rows + PR-map artifact (gate: approve)
Run the phases in order; start each only after the previous reports success. The gates live inside each sub-skill — you just relay their results. A sub-skill that ends without its success line declined a gate: stop and report.
Phase 1 — PRD
Invoke to-prd via the Skill tool. Pass the user's [description or context] and
any --title / --label. Capture N from its final line —
PRD published: <url> (issue #N). If to-prd reports a declined gate (no issue
published), stop. If it published but the line won't parse, confirm N with the
user before continuing.
Phase 2 — Slices
Invoke to-issues with --issue=N. It appends the slice plan and reports
Slices appended to issue #N. Proceed on that; stop if it reports a declined gate.
Phase 3 — PR breakdown
Invoke pr-breakdown with --issue=N. It appends the PR rows, publishes the
PR-map artifact, and reports PR breakdown appended to issue #N with the map URL —
relay that URL. Stop if it reports a declined gate.
If a gate is declined or a phase fails
Stop and report. Whatever already completed stays valid: a declined Phase 1 leaves nothing, Phase 2 leaves the PRD, Phase 3 leaves PRD + slices — any is a fine stopping point.
Common mistakes
| Mistake | Fix |
|---|---|
Not threading --issue=N into Phases 2–3 |
Capture N from Phase 1 and pass it on |
| Nesting skills (skill → skill → skill) | Invoke each phase's skill directly |
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 · 55 lines · 44 tokens per session scan A ac3add350873
breakdown is a skill published in the GitHub repository a1f/agent-templates (2 stars, last pushed 2mo ago), licensed MIT. It adds 44 tokens to every session and 571 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
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
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.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.