compound

A command that reviews completed SoloFlow sprints and groups possible follow-up work into clean-ups, backlog tasks, and instruction updates. SoloFlow is a workflow for managing development sprints.

In plain words
What is it for?
Combining findings from one or more sprints, proposing changes for approval, applying approved clean-ups and instruction edits, and sending backlog work to a task-refiner.
Why use it?
It turns scattered findings from finished sprints into one reviewable set of proposed improvements.

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/kesteva/soloflow/compound
Clone the repo
git clone --depth 1 https://github.com/kesteva/soloflow
Per session 64 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 8,869 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.00064 $0.08869
Opus 5 $0.00032 $0.04435
Sonnet 5 $0.00013 $0.01774
Haiku 4.5 $0.00006 $0.00887

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

Security

Grade A, and why

compound 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 2d 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.

commands/compound.md · 376 lines

How it starts

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

/soloflow:compound

Phase 6 of the SoloFlow pipeline. Reads done reports, stuck reports, human review notes, and out-of-scope findings queues, then produces a three-bucket proposal for the user to review one bucket at a time. The main agent (you) applies approved items directly for clean-ups and CLAUDE.md edits, and spawns the task-refiner for backlog tasks.

Batching. When two or more sprints are pending, --all (or a multi-select picker) batches them into ONE compounder invocation → ONE merged proposal (SPRINT-{MIN}-{MAX}-proposal.md) → ONE review flow → ONE apply pass. Each sprint's findings file still archives individually. Single-sprint runs are unchanged (no span, no batching logic engages).

Target: $ARGUMENTS (optional — sprint selector). Accepted values:

  • SPRINT-NNN — compound that specific sprint (single-sprint path)
  • --all — batch every pending sprint into one merged proposal
  • --oldest — silently pick the oldest pending sprint (single-sprint path)
  • empty — single pending sprint auto-selected; multi-select picker when two or more exist (user can pick a subset, all, or type free-text IDs for unusual subsets)

Model resolution (applies to every Agent spawn below)

Before invoking the Agent tool, resolve models.<name> per the three-tier recipe in docs/CUSTOMIZATION.md#config-resolution and pass the resolved value as the Agent tool's model parameter.

Mapping used in this command:

  • compoundermodels.compounder (fallback: sonnet)
  • claude-md-reviewermodels.claude_md_reviewer (fallback: opus) — pre-review of Bucket C in Step 2.5
  • compound-skepticmodels.compound_skeptic (fallback: opus) — per-item IMPLEMENT / DONT_IMPLEMENT verdicts in Step 2.6
  • task-refinermodels.task_refiner (fallback: opus) — used when materializing backlog items

Limits resolution

Resolve limits.context_limit_respawn_max (fallback: 3) at run start and use it wherever "Cap at 3 respawns" appears below.

Read the full file on GitHub · 376 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. 2d ago First seen · 376 lines · 64 tokens per session scan A 9930fc8fccf8

Subscribe to this mod's changes

compound is a command published in the GitHub repository kesteva/soloflow (40 stars, last pushed 3mo ago), licensed MIT. It adds 64 tokens to every session and 8,869 once invoked, about $0.0003 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.