decompose

A workflow for breaking a Piyaz project description into a connected set of software tasks. The result is a plan showing what needs to be built and how the tasks relate.

In plain words
What is it for?
Use it to decompose a project, create a task list, plan the build, or decide how the work should be divided.
Why use it?
It removes the need to turn a broad idea into an implementation plan manually. It makes the work easier to start and organize.

Agent

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 agents/frkak/piyaz/decompose
Clone the repo
git clone --depth 1 https://github.com/FrkAk/piyaz
Per session 170 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 7,263 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin unknown 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.00170 $0.07263
Opus 5 $0.00085 $0.03632
Sonnet 5 $0.00034 $0.01453
Haiku 4.5 $0.00017 $0.00726

Measured 3d ago against content hash a9ddc7f50126, 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 3d 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.

plugins/claude-code/agents/decompose.md · 536 lines

The source is not reproduced here

Licensed AGPL-3.0

The repository is licensed AGPL-3.0, which this catalogue does not treat as permission to reproduce the file. Read it at the source.

Read it on GitHub

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. 3d ago First seen · 536 lines · 170 tokens per session scan A a9ddc7f50126

Subscribe to this mod's changes

decompose is an agent published in the GitHub repository FrkAk/piyaz (188 stars, last pushed 4d ago), licensed AGPL-3.0. It adds 170 tokens to every session and 7,263 once invoked, about $0.0009 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.

Related

Other agents, from other repositories

output-ux-reviewer

Review a cli-web- CLI from the end-user perspective by RUNNING it. Owns end-to-end output VALIDITY: --help completeness, REPL help sync and REPL UX, --json output parseability, protocol leak detection, and entry point correctness (envelope STRUCTURE in code belongs to harness-compliance-reviewer). Returns scored…

ItamarZand88/CLI-Anything-WEB · 85 tokens

traffic-fidelity-reviewer

Review a cli-web- CLI implementation against its APP.md API map. Checks endpoint coverage, parameter fidelity, response parsing accuracy, dead client methods, and stale API map entries. Returns scored findings. Use during Phase 4 standards review — dispatched by the standards skill.

ItamarZand88/CLI-Anything-WEB · 59 tokens

star-implementer

Executes one step of a STAR execution plan under a written dispatch brief — changes only the files the brief names.

wanghao9610/STAR · 27 tokens

pm-orchestrator

Use this agent to plan, sequence, and orchestrate the whole AI team across the SDD lifecycle. It owns planning-first governance (roadmap → plan → approval → execution), GitHub issue/label governance, and delegation to the eight specialist agents. It drives the document lifecycle through the plugin's native SDD skills…

vladm3105/aidoc-flow-framework · 79 tokens

preflight

Preflight agent for /next. Runs the mechanical-drift scan and applies obvious fixes, runs the guidance-contradiction check, and reviews any ready worker result. Logs its own decisions to the orchestrator log and returns ONLY a compact report — raw scan output, contradiction reasoning, and diffs stay in this agent's…

dppdppd/rpm · 89 tokens

researcher

Gathers context from planning artifacts, codebase, and the web to inform planning decisions. Invoke at the start of /brainstorm, /specify, /design, /plan, /poke-holes, or any skill that needs a compound view of existing research, specs, designs, plans, and related code before new work begins.

danweinerdev/claude-sdd-planner · 71 tokens