Borrowing it
Nothing to install: this file belongs to asynkron/Asynkron.JsEngine. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/asynkron/Asynkron.JsEngine/main/.claude/skills/breakdown-issues/commands/breakdown-issues.mdgit clone --depth 1 https://github.com/asynkron/Asynkron.JsEngineWrote 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/commands/asynkron/asynkron.jsengine/breakdown-issues)<a href="https://agentmods.dev/commands/asynkron/asynkron.jsengine/breakdown-issues"><img src="https://agentmods.dev/badge/commands/asynkron/asynkron.jsengine/breakdown-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/commands/asynkron/asynkron.jsengine/breakdown-issues"><img src="https://agentmods.dev/badge/commands/asynkron/asynkron.jsengine/breakdown-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.00012 | $0.01301 |
| Opus 5.5 | $0.00005 | $0.00520 |
| Sonnet 5.5 | $0.00002 | $0.00260 |
| Haiku 4.5 | $0.00001 | $0.00130 |
Grade A, and why
breakdown-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 14d 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 — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue Breakdown Skill
Break down GitHub issues recursively until all leaf tasks are either simple (actionable) or research (need investigation).
Complexity Labels
The following complexity labels must exist in the repository:
simple- Task completable in a focused coding session (1-2 hours)moderate- Task requires multiple steps but is well-understoodcomplex- Task requires significant effort or has many sub-componentsresearch- Task needs investigation before it can be broken down
Rules
-
Stop conditions - Stop breaking down when a task is:
- Labeled
simple(actionable in one session) - Labeled
research(needs investigation first) - Already has 2+ child issues
- Labeled
-
Keep breaking down when a task is:
moderateorcomplexAND- Has 0-1 child issues
-
No AI slop - Sub-tasks must be:
- Clear, actionable work items
- Sum of children = parent functionality
- Follow naming conventions (e.g., "Task 1.2.3: Do something")
-
Hierarchical naming:
- Parent: "Task 1: Main work"
- Children: "Task 1.1: Sub-work", "Task 1.2: Other sub-work"
- Grandchildren: "Task 1.1.1: Detailed work"
-
Mark as research when:
- Root cause is unknown
- Multiple competing approaches with no clear winner
- You lack context to make informed breakdown decisions
-
CRITICAL: Trackable Relationships:
- Parent issues MUST have a task list with checkbox references to children
- This creates a real GitHub relationship that tracks progress
- When children are closed, the parent shows completion percentage
- Just mentioning "Parent: #123" in the child body is NOT enough
Process
Step 1: Scan Open Issues
gh issue list --state open --limit 100 --json number,title,labels
Step 2: Identify Issues Needing Breakdown
For each issue, check:
- Is it
moderateorcomplex? - Does it have 0-1 children?
- Is it NOT
simpleorresearch?
If all true → needs breakdown.
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.
- 14d ago First seen · 165 lines · 12 tokens per session scan A 33c091d02ff0
breakdown-issues is a command published in the GitHub repository asynkron/Asynkron.JsEngine (11 stars, last pushed 3mo ago), licensed MIT. It adds 12 tokens to every session and 1,301 once invoked, about $0.0000 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-10-02.
Other commands, from other repositories
template
Manage issue templates for streamlined issue creation.
fest-show
Show festival progression (in-progress tasks, roadmap, and dependency view).
add-note
Add an internal or external note to a ConnectWise PSA ticket.
sync-linear
Sync current work with Linear ticket status.
dispatcher
Use when you want the orchestrator to pick the next repo to work on across your whole portfolio — it enumerates candidate repos below the confinement root, resolves free/busy from each repo's session.lock lease, ranks the FREE ones by backlog priority × staleness × readiness, recommends the single most worthwhile one…
workpm
A project-management workflow for coordinating multiple AI workers through five stages. It includes task assignment, shared activity logs, worker replacement, and final checks.