implement

A command that carries out a stored coding plan and coordinates implementation review, fixes, checks, and the final report.

In plain words
What is it for?
Use it to turn a saved plan into code, have the result reviewed, address review findings, and perform final verification.
Why use it?
It keeps the implementation process tied to an approved plan and adds a review gate before the changes are committed.

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/vsladkov/claudex-stereo/implement
Clone the repo
git clone --depth 1 https://github.com/vsladkov/claudex-stereo
Per session 15 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 15,037 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.00015 $0.15037
Opus 5 $0.00008 $0.07519
Sonnet 5 $0.00003 $0.03007
Haiku 4.5 $0.00002 $0.01504

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

Security

Grade A, and why

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

plugins/stereo/commands/implement.md · 1,081 lines

How it starts

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

First Read ${CLAUDE_PLUGIN_ROOT}/skills/model-routing/SKILL.md and apply its routing, foreground agent, validation, quoting, and background-job rules. The rules below are step-specific.

Run the implementation phase of the Stereo workflow. The main Claude session owns preflight, baselines, host verification, review/fix orchestration, and the final report.

Raw slash-command arguments: $ARGUMENTS

Arguments and modes

After reading the routing skill, parse all arguments before loading state:

  • --implementer <model> selects the implementer. Resolve it as explicit flag > workspace implementer default > claude:opus.
  • --implementer-effort <none|minimal|low|medium|high|xhigh|max> overrides effort for a Codex-routed implementer.
  • --implementation-reviewer <model> selects the implementation reviewer. Resolve it as explicit flag > workspace implementationReviewer default > codex:sol: the implementation review is the last gate before commit, and the cross-ecosystem reviewer is independent of both the orchestrator and the Claude-routed default implementer that produced the delta. claude:session remains valid and is the cheaper inline choice.
  • --implementation-reviewer-effort <none|minimal|low|medium|high|xhigh|max> overrides effort for a Codex-routed implementation reviewer.
  • --effort <none|minimal|low|medium|high|xhigh|max> is the command-wide default for Codex-routed roles that have no role effort flag. When no active role is Codex-routed, a command-wide --effort is inert: accept it, report it as inert, and never translate it into a Claude-side control.
  • --max-fix-rounds <n> defaults to 4. Direct gate-fix turns and review-driven fix turns both count toward it; the implementer's own inner-loop iterations never do.
  • --slot <name> selects the stored plan to implement and defaults to default.
  • --fresh skips a reusable stored Codex plan-review thread; it only affects a Codex-routed implementer and is accepted but reported as inert for a Claude-routed one.
  • --implement-only implements and verifies once, then stops before review.
  • --review-only reviews the current dirty/untracked implementation delta once without fixing.
  • --resume re-enters a recorded incomplete implementation phase after a crashed, compacted, or closed Claude session.
  • --isolated runs implementation in a throwaway detached git worktree outside the repository and hands the delta back as a user-confirmed patch. It never commits and never writes in the main working tree.
  • --base <ref> reviews the committed <ref>...HEAD range and is valid only with --review-only.
  • Without a mode flag, run the complete implement-plus-review/fix phase.

Define <slotArg> as --slot <slot> for a non-default target slot and omit it entirely for the default slot. On --resume, replace it with the slot owned by the durable implementation record.

Reject missing values, duplicates, positionals, invalid effort/round values, unknown flags, unknown claude:* values, and both mode flags together. Accept claude:inherit alongside claude:session and the four explicit Claude aliases. Accept a Codex selection with or without the codex: prefix and reject codex:claude:*. The removed implementer --model and --review-model flags are unknown; report the role-named replacements. The renamed --impl-reviewer and --impl-reviewer-effort flags are unknown; report --implementation-reviewer and --implementation-reviewer-effort as their replacements.

For --review-only, reject --implementer, --implementer-effort, --fresh, and --max-fix-rounds. For --implement-only, reject --implementation-reviewer, --implementation-reviewer-effort, and --max-fix-rounds. Reject a role effort flag when its selected role is Claude-routed.

Reject --resume with --implement-only, --review-only, or --fresh. Reject --resume with --implementer or --implementer-effort: the durable record owns the implementer; tell the user to run without --resume to start over. Reject --resume with --slot: the durable record owns the plan slot; tell the user to run without --resume to start over. --implementation-reviewer, --implementation-reviewer-effort, --effort, and --max-fix-rounds remain legal with --resume. Reject --base without --review-only. Reject --scope in every mode and name --base <ref> as the supported standalone range control: auto-detecting a default base could silently review commits the plan never covered.

Read the full file on GitHub · 1,081 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 · 1,081 lines · 15 tokens per session scan A fa906acf58e6

Subscribe to this mod's changes

implement is a command published in the GitHub repository vsladkov/claudex-stereo (3 stars, last pushed 23d ago), licensed Apache-2.0. It adds 15 tokens to every session and 15,037 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.