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 skills/ninthwave-io/ninthwave/decomposenpx skills add ninthwave-io/ninthwave --skill decomposegit clone --depth 1 https://github.com/ninthwave-io/ninthwaveWrote 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/skills/ninthwave-io/ninthwave/decompose)<a href="https://agentmods.dev/skills/ninthwave-io/ninthwave/decompose"><img src="https://agentmods.dev/badge/skills/ninthwave-io/ninthwave/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 | $0.00075 | $0.04975 |
| Opus 5 | $0.00037 | $0.02488 |
| Sonnet 5 | $0.00015 | $0.00995 |
| Haiku 4.5 | $0.00007 | $0.00498 |
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 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 — 354 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Interactive Questions (CRITICAL)
This skill is highly interactive. You MUST use your interactive question tool to ask the user questions -- do NOT simply print a question as text and wait for a response.
Tool names by platform: AskUserQuestion (Claude Code), question (OpenCode), request_user_input (Codex), ask_user (Copilot CLI, Gemini CLI). Use whichever is available in your environment.
Every question must follow this structure:
- Re-ground: State the project, the current branch, and what phase you're in. Assume the user hasn't looked at this window in 20 minutes.
- Explain simply: Describe the situation in plain English. Say what it does, not what it's called.
- Recommend: State which option you'd pick and why. Include a one-line reason.
- Options: Lettered options: A), B), C). When an option involves effort, indicate the scale.
Instructions
This skill decomposes a feature spec into work items sized for individual human-reviewable PRs. Each item is written as an individual file in .ninthwave/work/, ready for orchestration via nw.
Treat .ninthwave/work/ as the live queue of open work: /decompose populates it, nw works through it, and completed work is intentionally looked up through merged PRs, nw history, nw logs, and git history rather than retained in a done lane.
Prerequisites: ninthwave (or nw) must be in PATH. .ninthwave/work/ directory must exist.
Phase 1: INTAKE
Goal: Identify and understand the feature to decompose.
-
The user may provide:
- A file path to a spec/PRD/phase doc
- A reference to a project doc
- A verbal description of the feature
-
If a file path or doc reference is provided, read it.
-
If the description is verbal/ambiguous, AskUserQuestion to clarify scope.
-
Summarize the feature scope in 3-5 bullet points and confirm with the user.
-
Internalize external specs. If the spec or plan doc lives outside the repo (absolute path, home directory,
~/.claude/, etc.), it must be brought into the repo so workers can access it. Workers clone from remote into isolated worktrees -- they cannot read files outside the repo.
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 · 354 lines · 75 tokens per session scan A 1d46fd31136a
decompose is a skill published in the GitHub repository ninthwave-io/ninthwave (8 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 75 tokens to every session and 4,975 once invoked, about $0.0004 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.
Other skills, from other repositories
armada-gate
Run an evidence-gate checklist for each success criterion in the current phase. Use when checking if a phase is complete before marking it passed.
declare
Analyzes task plan and declares files that will be created or modified, producing declared-files.json.
execute
Executes the implementation plan for a Formic task.
openspec-new-change
Start a new OpenSpec change using the experimental artifact workflow. Use when the user wants to create a new feature, fix, or modification with a structured step-by-step approach.
openspec-apply-change
Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.
moai-kanban-foreman
One unattended kanban foreman iteration: watch the backlog queue, dispatch the next operator-picked card to an isolated worker, collect completion evidence on read (not on claims), and report. This is the body the project's loop.md driver invokes each iteration of a bare /loop; it can also be invoked directly to test…