decompose

A command for splitting a project or feature into smaller sub-features and producing a feature manifest. A manifest is a structured list of features and their dependencies.

In plain words
What is it for?
Use it when a project may need decomposition into smaller deliverables before implementation. It invokes the `spec-forge:decompose` workflow with the supplied project or feature name.
Why use it?
It makes a potentially broad piece of work easier to understand and exposes which parts depend on others. The description does not specify how the project is split.

Command

Install

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.

agentmods
npx agentmods add commands/tercel/spec-forge/decompose
Clone the repo
git clone --depth 1 https://github.com/tercel/spec-forge
Per session 20 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 107 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00020 $0.00107
Opus 5 $0.00010 $0.00053
Sonnet 5 $0.00004 $0.00021
Haiku 4.5 $0.00002 $0.00011

Measured yesterday against content hash 2a000def24d0, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 yesterday.

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.

commands/decompose.md · 12 lines

What it actually says

Invoke the spec-forge:decompose skill and follow it exactly as presented to you.

The user invoked this command with: $ARGUMENTS

Treat $ARGUMENTS as the project/feature name to decompose. Pass it directly to the skill.

Changes

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.

  1. yesterday First seen · 12 lines · 20 tokens per session scan A 2a000def24d0

Subscribe to this mod's changes

decompose is a command published in the GitHub repository tercel/spec-forge (5 stars, last pushed 1mo ago), licensed MIT. It adds 20 tokens to every session and 107 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-31.