decompose: Skill for Claude Code

.claude/skills/decompose/SKILL.md

decompose is a skill for Claude Code from sciyoshi/decompose. It costs 35 tokens per session (936 once invoked), scanned A, original, Apache-2.0.

A command-line tool for running and supervising several local development processes, with compatibility for many Docker Compose-style files. It runs native processes rather than containers.

In plain words
What is it for?
Use it to bring services up or down, check their status, follow all or one service's logs, and investigate process problems.
Why use it?
It gives you one place to start, stop, restart, inspect, and follow logs from local services instead of managing each process separately.

Skill for Claude Code

Written for Claude Code: installed under .claude/.

This is sciyoshi/decompose's own configuration. It tells Claude Code how to work on decompose itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything decompose configures →

Reuse

Borrowing it

Nothing to install: this file belongs to sciyoshi/decompose. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/sciyoshi/decompose/main/.claude/skills/decompose/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/sciyoshi/decompose

Made for: Claude Code.

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

agentmods badge for decompose

README.md
[![agentmods](https://agentmods.dev/badge/skills/sciyoshi/decompose/decompose/github.svg)](https://agentmods.dev/skills/sciyoshi/decompose/decompose)
Your own site
<a href="https://agentmods.dev/skills/sciyoshi/decompose/decompose"><img src="https://agentmods.dev/badge/skills/sciyoshi/decompose/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.

agentmods 80×15 button for decompose

Your own site · 80×15
<a href="https://agentmods.dev/skills/sciyoshi/decompose/decompose"><img src="https://agentmods.dev/badge/skills/sciyoshi/decompose/decompose.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 35 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 936 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00035 $0.00936
Opus 5.5 $0.00014 $0.00374
Sonnet 5.5 $0.00007 $0.00187
Haiku 4.5 $0.00003 $0.00094

Measured yesterday against content hash 60815c82d57f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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.

.claude/skills/decompose/SKILL.md · 95 lines

How it starts

The opening of the file, as written. The whole thing — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are helping the user manage their local development environment using decompose, a process orchestrator that is broadly compatible with Docker Compose but runs native processes.

Quick reference

decompose up -d                    # Start all services detached
decompose up -d SERVICE...         # Start specific services (+ deps)
decompose up -d --no-deps SERVICE  # Start without pulling in deps
decompose down                     # Stop everything, tear down daemon
decompose ps                       # Show process status
decompose ps --json                # Machine-readable status
decompose logs -f                  # Follow all logs
decompose logs -f SERVICE          # Follow specific service logs
decompose logs -n 100 SERVICE      # Last 100 lines of a service
decompose start SERVICE            # Start a stopped service
decompose stop SERVICE             # Stop a running service
decompose restart SERVICE          # Restart a service
decompose attach                   # Reattach to daemon log stream

How decompose works

  • decompose up spawns a background daemon that manages all processes. The CLI is a thin client that talks to the daemon over a local Unix socket.
  • Each environment is identified by a hash of the config directory + files, or by --session NAME (the name is used as the ID).
  • Config is discovered automatically: decompose.yml > decompose.yaml > compose.yml > compose.yaml. Use -f FILE to override (can be repeated for overlay merging).
  • Output modes: --json (machine), --table (human), or auto-detect (TTY/CI/LLM -> table, pipe -> JSON).

When the user asks to start/debug their environment

  1. Check if a compose file exists in the working directory. Look for decompose.yml, decompose.yaml, compose.yml, or compose.yaml.
  2. Check if a daemon is already running: decompose ps --json. If it returns "running": true, services are already up.
  3. Start services: decompose up -d for detached mode.
  4. Check status: decompose ps to verify everything is running.
  5. View logs: decompose logs -f SERVICE to debug startup issues.
  6. Look for errors: Check if processes are in stopped or exited status. Use logs to find the root cause.

Read the full file on GitHub · 95 lines

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 · 95 lines · 35 tokens per session scan A 60815c82d57f

Subscribe to this mod's changes

decompose is a skill published in the GitHub repository sciyoshi/decompose (7 stars, last pushed 12d ago), licensed Apache-2.0. It adds 35 tokens to every session and 936 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-11-07.

Related

decompose compared with skills from other repositories

decompose next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
decomposesciyoshi/decomposeSkill712d agoApache-2.0A35Claude Code
imagegenopenai/codexSkill134ktodayApache-2.0A113Codex
local-ai-agentsmicrosoft/ai-agents-for-beginnersSkill79kyesterdayMITA200Claude Code, Codex
playwright-climicrosoft/playwrightSkill100kyesterdayApache-2.0A19Claude Code
browser-automationopenclaw/openclawSkill394ktodayMITA36Claude Code
systematic-debuggingobra/superpowersSkill314k4d agoMITA21Claude Code
next-cache-components-adoptionvercel/next.jsSkill143ktodayMITA95Claude Code