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 agentmods add commands/ngocsangyem/meowkit/breakdowngit clone --depth 1 https://github.com/ngocsangyem/MeowKitWrote 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/ngocsangyem/meowkit/breakdown)<a href="https://agentmods.dev/commands/ngocsangyem/meowkit/breakdown"><img src="https://agentmods.dev/badge/commands/ngocsangyem/meowkit/breakdown.svg" alt="Measured on agentmods" 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 | $0.00028 | $0.00641 |
| Opus 5 | $0.00014 | $0.00320 |
| Sonnet 5 | $0.00006 | $0.00128 |
| Haiku 4.5 | $0.00003 | $0.00064 |
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 4d 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/mk:breakdown — Spec to stories + optional tickets + tech breakdown
When to use
Use when you have a Confluence page, Jira epic, GitHub issue, Linear ticket, or pasted PRD and want: (1) refined user stories, (2) optional Jira tickets, (3) codebase-aware tech breakdown report. Stops before plan creation.
- NOT for sprint capacity planning →
mk:planning-engine - NOT for bulk ticket creation →
mk:story-sizer --auto-create - NOT for implementation planning →
/mk:plan - NOT for single-ticket analysis or RCA →
mk:intakeormk:jira-analyst
Usage
/mk:breakdown <source> [--source confluence|jira|github|linear|paste] [--project <KEY>]
<source>: Confluence URL/page-id, Jira KEY, GitHub issue URL, Linear URL, file path, or omit when using--paste.--source: Override auto-detection.--project <KEY>: Required when Jira creation confirmed in Phase D. If absent at first Create, Phase D aborts; spec analysis is preserved; Phase E emits a re-run footer.
Idempotency: Same-day re-run overwrites breakdown-{YYMMDD}-{slug}.md. Tickets already in Jira remain — pick "Skip" for existing stories on re-run.
Purpose
Analyze a spec or issue source, derive user stories, optionally create Jira tickets, optionally run tech planning, and write a breakdown report.
Dispatch
Use task-specific skills instead of duplicating their procedures here:
- Source analysis
- Confluence sources →
mk:confluence-spec-analyst - Jira/GitHub/Linear/paste/file sources →
mk:intake
- Confluence sources →
- Story decomposition — extract story title, acceptance criteria, complexity hint, and open questions from the source analysis.
- Optional ticket creation — for each accepted story, use
mk:jira-issue; require--project <KEY>before creating tickets. - Optional tech breakdown — after tickets exist, use
mk:planning-engine plan --tickets <keys>. - Report write — save
tasks/reports/breakdown-{YYMMDD}-{slug}.mdor the active plan'sresearch/directory.
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.
- 4d ago First seen · 55 lines · 28 tokens per session scan A ee39083a319b
breakdown is a command published in the GitHub repository ngocsangyem/MeowKit (14 stars, last pushed 1mo ago), licensed MIT. It adds 28 tokens to every session and 641 once invoked, about $0.0001 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-30.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.