implement

implement is a command for Claude Code, Codex from vsladkov/claudex-stereo. It costs 15 tokens per session (5,782 once invoked), scanned A, original, Apache-2.0.

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 for Claude CodeCodex

Written for Claude Code and Codex: allowed-tools in frontmatter, but also reads $CODEX_HOME. Also seen: names the AskUserQuestion tool; mentions Codex.

Runs only inside its plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else. Install the plugin, not this.

Part of the stereo plugin — 4 skills, 15 commands, 1 agent, 3 hooks shipped together

Good fit Use it to turn a saved plan into code, have the result reviewed, address review findings, and perform final verification.

Compare 6 commands from other repositories ↓
Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code
/plugin marketplace add vsladkov/claudex-stereo
Claude Code
/plugin install stereo

Made for: Claude Code, Codex.

Or install stereo, the plugin that ships this one along with the rest of its 4 skills, 15 commands, 1 agent, 3 hooks.

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 implement

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

Your own site · 80×15
<a href="https://agentmods.dev/commands/vsladkov/claudex-stereo/implement"><img src="https://agentmods.dev/badge/commands/vsladkov/claudex-stereo/implement.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
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 5,782 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.00015 $0.05782
Opus 5.5 $0.00006 $0.02313
Sonnet 5.5 $0.00003 $0.01156
Haiku 4.5 $0.00002 $0.00578

Measured 21d ago against content hash 4be7df3e3f00, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 21d 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 · 366 lines

How it starts

The opening of the file, as written. The whole thing — 366 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, then ${CLAUDE_PLUGIN_ROOT}/skills/model-routing/pair-procedures.md and ${CLAUDE_PLUGIN_ROOT}/skills/model-routing/implement-procedures.md — plus ${CLAUDE_PLUGIN_ROOT}/skills/model-routing/worktree-procedure.md for an --isolated run or the resume of an isolated record — and apply their rules. The rules below are step-specific; a quoted heading names the section of a routing file that defines the step.

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

Parse all arguments per "Selection and effort parsing" before loading state, then read the "Workspace role defaults" and say in the final effective-role note when a workspace default supplied the implementer:

  • --implementer <model> and --implementer-effort <effort> select the implementer and its effort.
  • --implementation-reviewer <model> and --implementation-reviewer-effort <effort> select the implementation reviewer and its effort. Its built-in default is a Codex model: the implementation review is the last gate before commit, and the cross-ecosystem reviewer is independent of both the orchestrator and the default Claude implementer. claude:session is the cheaper inline choice.
  • --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.
  • --implement-only implements and verifies once, then stops before review.
  • --review-only reviews the current dirty/untracked implementation delta once without fixing.
  • --base <ref> reviews the committed <ref>...HEAD range and is valid only with --review-only.
  • --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 and hands the delta back as a user-confirmed patch.
  • Without a mode flag, run the complete implement-plus-review/fix phase.

Reject positionals and both mode flags together. Reject --fresh: the implementer always starts fresh. For --review-only, reject --implementer, --implementer-effort, and --max-fix-rounds. For --implement-only, reject --implementation-reviewer, --implementation-reviewer-effort, and --max-fix-rounds. Reject --base without --review-only, and reject --scope in every mode, naming --base <ref> as the supported standalone range control: auto-detecting a default base could silently review commits the plan never covered. Reject --isolated with --review-only and with --base.

Reject --resume with --implement-only, --review-only, --implementer, --implementer-effort, or --slot: the durable record owns the implementer and the plan slot, so tell the user to run without --resume to start over. --implementation-reviewer, --implementation-reviewer-effort, and --max-fix-rounds stay legal with it. A bare --resume against an isolated record resumes in its recorded worktree and says so; reject --isolated --resume against a non-isolated record and tell the user to run without --resume to start an isolated phase. On resume, the recorded implementer — its launchArgs and userOwnedSteps — stays fixed for later fixes, while the implementation reviewer is resolved, granted, and pinned afresh ("Pinned selections"); its recorded selection is historical context.

Inside the full fix loop, act on findings automatically. In --review-only and at explicit safeguard decisions, stop after presenting review findings and let the user decide what changes.

Read the full file on GitHub · 366 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. 21d ago Changed · -715 lines 4be7df3e3f00
  2. 1mo ago Changed · -1 lines 74802c8baf7c
  3. 1mo ago Changed · +1 lines da36f2d83837
  4. 1mo 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 (4 stars, last pushed 21d ago), licensed Apache-2.0. It adds 15 tokens to every session and 5,782 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-08-31.