Borrowing it
Nothing to install: this file belongs to tatargabor/set-core. 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/tatargabor/set-core/main/.claude/commands/set/decompose.mdgit clone --depth 1 https://github.com/tatargabor/set-coreWrote 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/tatargabor/set-core/decompose)<a href="https://agentmods.dev/commands/tatargabor/set-core/decompose"><img src="https://agentmods.dev/badge/commands/tatargabor/set-core/decompose.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.1 | $0.00000 | $0.00147 |
| Opus 5 | $0.00000 | $0.00073 |
| Sonnet 5 | $0.00000 | $0.00029 |
| Haiku 4.5 | $0.00000 | $0.00015 |
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 today.
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.
Copies of this mod
1 near-identical copy found in the catalogue:
- decompose — 100% identical, 0 lines differ
What it actually says
Decompose a specification into an orchestration execution plan using agent-based analysis.
Usage: /set:decompose [spec-path]
This runs the decomposition skill which:
- Reads the spec document
- Explores the codebase for existing implementations
- Checks project knowledge, requirements, and project type
- Recalls relevant planning memories
- Generates
orchestration-plan.json
If no spec path is provided, it will look for the spec configured in orchestration config.
Arguments:
- spec-path: Path to the spec file (e.g.,
set/orchestration/specs/v12.md)
Example: /set:decompose set/orchestration/specs/v12-minicrm.md
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.
- today First seen · 18 lines · 0 tokens per session scan A 8ca22a22519a
decompose is a command published in the GitHub repository tatargabor/set-core (35 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 147 tokens. 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-09-06.
Other commands, from other repositories
hatch3r-feature-plan
Design a new capability -- draft user stories, acceptance criteria, data model, API surface, and sub-issue breakdown as an epic-shaped todo.md for greenfield features.
hatch3r-spec
Spec orchestrator — detects greenfield vs brownfield project state and runs the corresponding spec agent to produce requirements, acceptance criteria, risk inventory, and test plan (greenfield adds market/competitive/persona/tech-stack; brownfield adds…
story-6.1.4
Story ID: 6.1.4 Epic: Epic-6.1 - Agent Identity System Wave: Wave 1 (Foundation) Status: 📋 Ready to Start Priority: 🔴 Critical Owner: Dev (Dex) Created: 2025-01-14 Updated: 2025-01-17 (v4 - Unified System Integration) Duration: 2.5 days (20 hours) Investment: $250.00.
story-7.1.1
Story ID: 7.1.1 Epic: Epic-7 - Dashboard Workspace Integration Wave: Wave 1 (Foundation) Status: ⌛ In Progress Priority: 🔴 High Owner: Architect (Aria) → Dev (Dex) Created: 2026-05-05 Updated: 2026-05-05.
hatch3r-plan
Planning router — classifies a free-form planning request, confirms the match, and drives the matching planning flow(s) (feature-plan, bug-plan, migration-plan, refactor-plan, test-plan, api-spec, project-spec, roadmap, spec) with shared intake context, producing one consolidated outcome and a single plan-execution…
mpm-init
Initialize or update project for Claude Code and MPM.