cc-implement

An implementation command for carrying out tasks from an approved plan. It also restores saved context for the current code revision before work begins.

In plain words
What is it for?
Use it to execute an approved coding plan and resume work from saved project context.
Why use it?
It helps the agent continue planned implementation work with the relevant earlier state available.

Command for Claude Code

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/yeisonrestrepo/code-conductor/cc-implement
Clone the repo
git clone --depth 1 https://github.com/yeisonrestrepo/code-conductor

Made for: Claude Code.

Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 2,828 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. 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.00011 $0.02828
Opus 5 $0.00005 $0.01414
Sonnet 5 $0.00002 $0.00566
Haiku 4.5 $0.00001 $0.00283

Measured yesterday against content hash 1c56b4980a3e, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade C, and why

cc-implement scanned grade C with 1 finding 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.

Hidden instructionshighPrompt injection

Directives inside HTML comments, invisible characters or bidirectional overrides are read by the model and not by the person reviewing the file.

3. Strip Unicode invisible characters: `​`, ` `, `‌`, `‍` **`old_string` construction** (Steps 3 and 5 — the actual string passed to `Edit`): - Take the Read result verbatim; strip trailing whitespace and `\r` only - Pre
.claude/commands/cc-implement.md · 165 lines

How it starts

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

Phase entry - Resume Read

Before doing anything else, restore any stored context for the current commit by running scripts/resume-read.mjs. It resolves the current git hash, prefers a valid DB snapshot (conductor-db get-snapshot), falls back to the .claude/memory/session-snapshot.json handoff file, and prints a RESUME_HIT block on a hit / nothing on a miss. Capture its stdout and its exit code with the canonical per-platform form (each first probes for node and treats its absence as a clean miss, never an error):

  • Unix / Git Bash:
    if command -v node >/dev/null 2>&1; then
      resume_out="$(node scripts/resume-read.mjs 2>>.conductor/last-write.log)"; resume_rc=$?
    else resume_rc=3; resume_out=""; fi
    
  • PowerShell:
    if (Get-Command node -ErrorAction SilentlyContinue) {
      $__eap = $ErrorActionPreference; $ErrorActionPreference = 'Continue'
      if (Test-Path variable:PSNativeCommandUseErrorActionPreference) {
        $__nap = $PSNativeCommandUseErrorActionPreference; $PSNativeCommandUseErrorActionPreference = $false
      }
      try {
        $resume_out = node scripts/resume-read.mjs 2>> .conductor/last-write.log; $resume_rc = $LASTEXITCODE
      } catch { $resume_rc = 3; $resume_out = "" }
      finally {
        $ErrorActionPreference = $__eap
        if (Test-Path variable:__nap) { $PSNativeCommandUseErrorActionPreference = $__nap }
      }
    } else { $resume_rc = 3; $resume_out = "" }
    

Branch on resume_rc - only 0 and 4 are meaningful; every other code proceeds fresh:

  • 0 → parse the captured block and adopt it as this phase's starting context, then echo one banner to the user: > Resumed from stored snapshot @ <commit> (phase: <phase>), appending (checkpoint prose available) when the block reports prose: available. Parsing (the command owns normalization): split on \n; strip a trailing \r from every line; drop leading/trailing wholly-blank lines; require lines[0].trim() === 'RESUME_HIT' (anything else = miss); key: value lines split on the first ': ' (both sides trimmed); the pending: block is every subsequent ^\s*-\s+ line up to the first blank line or EOF, each item trimmed. Unknown keys are ignored. In PowerShell, node … binds string[] for multi-line output - normalize with $lines = @($resume_out); a $null/empty capture with resume_rc = 3 is a miss.
  • 4operational halt. Do not run this phase's normal work. Emit exactly: SNAP_INVALID: corrupt handoff at .claude/memory/session-snapshot.json - inspect or remove it, then re-run. and enter standby awaiting user action. The corrupt file is left on disk (the script did not delete it).
  • 3 or any other codeproceed fresh (clean miss, bypass, degrade, absent node, or any unexpected runtime code). Ignore the capture.

resume-read.mjs writes its own trace lines to .conductor/last-write.log via appendFileSync; the 2>> redirect above only sinks the incidental exit-4 halt reason away from the UI - it is not the trace channel.


Read .claude/memory/project.md before starting any task.

Read the full file on GitHub · 165 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 · 165 lines · 11 tokens per session scan C 1c56b4980a3e

Subscribe to this mod's changes

cc-implement is a command published in the GitHub repository yeisonrestrepo/code-conductor (6 stars, last pushed 1mo ago), licensed MIT. It adds 11 tokens to every session and 2,828 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (hidden instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.