Borrowing it
Nothing to install: this file belongs to fotoetienne/gru. 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/fotoetienne/gru/main/.claude/commands/decompose.mdgit clone --depth 1 https://github.com/fotoetienne/gruWrote 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/fotoetienne/gru/decompose)<a href="https://agentmods.dev/commands/fotoetienne/gru/decompose"><img src="https://agentmods.dev/badge/commands/fotoetienne/gru/decompose/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/fotoetienne/gru/decompose"><img src="https://agentmods.dev/badge/commands/fotoetienne/gru/decompose.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.00013 | $0.01069 |
| Opus 5.5 | $0.00005 | $0.00428 |
| Sonnet 5.5 | $0.00003 | $0.00214 |
| Haiku 4.5 | $0.00001 | $0.00107 |
Grade A, and why
decompose 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Break a complex GitHub issue into smaller, manageable sub-issues.
Issue: $ARGUMENTS
Workflow:
1. Fetch & Analyze the Issue
- Use
gh issue view $ARGUMENTSto get the full issue details - Read the issue title, body, labels, and any comments
- Understand the full scope of what needs to be done
2. Assess Complexity
Analyze whether the issue should be decomposed:
- Does it involve multiple distinct components or systems?
- Does it have multiple acceptance criteria or requirements?
- Would it take more than a few hours to complete in one go?
- Does it mix different types of work (e.g., backend + frontend + docs)?
If the issue is straightforward and focused, inform the user that decomposition isn't needed.
3. Explore the Codebase
- Use the Task tool with
subagent_type='Explore'to understand:- What code/files are affected by this issue
- Existing architecture and patterns
- Dependencies between components
- This helps identify natural boundaries for breaking up the work
4. Propose Decomposition Plan
- Create a list of 2-5 smaller sub-issues that:
- Are independently implementable (minimize dependencies)
- Each have clear, testable outcomes
- Follow a logical implementation order
- Use TodoWrite to present the proposed breakdown
- Each todo should describe a potential sub-issue with:
- Clear title (what it does)
- Brief description (why it's separate)
- Dependencies (if any)
5. Get User Approval
- Use AskUserQuestion to confirm:
- Should we proceed with decomposition?
- Does the proposed breakdown make sense?
- Any adjustments needed?
6. Create Sub-Issues
For each approved sub-issue:
- Use
gh issue createwith:- Clear, specific title
- Body that includes:
- Description: What this sub-issue addresses
- Parent Issue: "Part of #"
- Blocked by: #X, #Y (links to prerequisite sub-issues if order matters, using the
**Blocked by:** #X, #Yconvention) - Code Areas: File/module references
- Labels: Copy from parent + add
subtaskif available
- Capture the new issue numbers
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 · 109 lines · 13 tokens per session scan A 8b4845461cbc
decompose is a command published in the GitHub repository fotoetienne/gru (11 stars, last pushed 27d ago), licensed Apache-2.0. It adds 13 tokens to every session and 1,069 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-30.
Other commands, from other repositories
epic-claim
Claim an epic issue, stamp coordination state, and sync local ownership.
epic-review
Mark epic review requested, approved, or changes requested.
portfolio
Show a read-only hub-wide portfolio of canonical Ideas and active Projects without duplicating topic-owned records.
create-plan
Writes an implementation plan as a file artifact in the task directory (.ork/tasks/TASK/NN-plan-SLUG.md) with phases, exact file changes and runnable success criteria, so reviewers comment on the file instead of in chat. Use when a task has its research done and needs a reviewable plan before code; pair with…
gh-triage
GitHub OSS maintainer lifecycle triage, review, and approval management.
amend-plan
Plan Amend - Discuss and apply amendments to a plan.json implementation plan.