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 kellykampen/agent-skills --skill issue-breakdowngit clone --depth 1 https://github.com/kellykampen/agent-skillsWrote 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/kellykampen/agent-skills/issue-breakdown)<a href="https://agentmods.dev/skills/kellykampen/agent-skills/issue-breakdown"><img src="https://agentmods.dev/badge/skills/kellykampen/agent-skills/issue-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/kellykampen/agent-skills/issue-breakdown"><img src="https://agentmods.dev/badge/skills/kellykampen/agent-skills/issue-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.00182 | $0.03053 |
| Opus 5 | $0.00091 | $0.01527 |
| Sonnet 5 | $0.00036 | $0.00611 |
| Haiku 4.5 | $0.00018 | $0.00305 |
Grade A, and why
issue-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 10d 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 — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue Breakdown
Turn a feature, epic, or rough initiative into one Linear project (the epic) and a set of small, review-ready issues that all clear a fixed quality bar. The value here is predictability: the same feature, broken down by anyone on any day, comes out as the same shape of tickets — small user stories with acceptance criteria, estimates, parents, dependency links, and (for design work) a picture of the target. A backlog built this way is estimable, parallelizable, and reviewable; a backlog of vague 8-point "build the thing" tickets is none of those.
Apply this whether you're creating the issues live (linear-cli or the Linear MCP) or just drafting specs to paste in later — the standard is the same; only the last "how to create it" step changes.
The shape you're producing
Epic (Linear project) ── what / why / how / key features
├─ Issue (≤3 pts, user story, AC, labels, parent, links)
├─ Issue (≤3 pts, …) ──blocks──▶ Issue
└─ Issue (≤3 pts, …)
Work top-down: first frame the epic, then decompose it into issues, then wire the dependencies between them. Don't create issues before the epic exists — an unparented issue is a rule violation and loses the "why."
Step 1 — Frame the epic (project)
The epic is the container and the narrative. Give it four things so anyone landing on it understands the work without reading every child:
-
What — the feature in one or two sentences.
-
Why — the user/business outcome it drives.
-
How — the approach and the key decisions already locked.
-
Key features / scope — a short bullet list of what's in, and an explicit non-goals line for what's out.
-
Project-level dependencies — which other existing projects in the team must this epic build on? Check the team's project list and link the ones it depends on. Nearly every project depends on ≥1 other; only a genuinely foundational epic is a legitimate solo. These are project↔project relations, distinct from the issue links in Step 2.5 — see the tool note in Step 4.
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.
- 10d ago First seen · 152 lines · 182 tokens per session scan A 85d63ffeeaae
issue-breakdown is a skill published in the GitHub repository kellykampen/agent-skills (2 stars, last pushed 1mo ago), licensed MIT. It adds 182 tokens to every session and 3,053 once invoked, about $0.0009 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
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.
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.