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.
npx agentmods add commands/yeisonrestrepo/code-conductor/cc-resumegit clone --depth 1 https://github.com/yeisonrestrepo/code-conductorWrote 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.
[](https://agentmods.dev/commands/yeisonrestrepo/code-conductor/cc-resume)<a href="https://agentmods.dev/commands/yeisonrestrepo/code-conductor/cc-resume"><img src="https://agentmods.dev/badge/commands/yeisonrestrepo/code-conductor/cc-resume.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00014 | $0.01322 |
| Opus 5 | $0.00007 | $0.00661 |
| Sonnet 5 | $0.00003 | $0.00264 |
| Haiku 4.5 | $0.00001 | $0.00132 |
Grade A, and why
cc-resume scanned grade A 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 4d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -fsSL --max-time 5 https://raw.githubusercontent.com/yeisonrestrepo/code-conductor/main/VERSION 2>/dev/null How it starts
The opening of the file, as written. The whole thing — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Step 1 — Verify project initialization
Check if CLAUDE.md exists in the current directory.
- If absent: stop immediately and output —
"Project not initialized. Run /cc-init first." - If present but
## Project Identityfields are all empty: continue and include this warning at the top of the final report:"⚠ Project identity incomplete — run /cc-init to fill it in."
Step 2 — Read project identity
Read CLAUDE.md. Extract:
- Name (from
- **Name:**) - Description (from
- **Description:**) - Stack (from
- **Stack:**) - Language (from
- **Language:**)
Use — for any missing fields.
Auto-fill blank command fields (BUG-015): After reading the identity fields, check if any of Build, Test, Lint, Format, Setup in CLAUDE.md are still <command> (any case) or blank after the colon. If at least one is blank AND scripts/detect-stack.mjs exists at $PWD:
- Run
node scripts/detect-stack.mjs "$PWD"and capture the JSON output. - For each blank/placeholder command field, if the JSON contains a matching key (
build,test,lint,format,setup), replace the placeholder with the detected value using a singleEditcall. - Never overwrite a field that already contains a non-placeholder value.
- If all five fields are already populated, or if
scripts/detect-stack.mjsdoes not exist, skip this step silently. - If the JSON is
{}or node exits non-zero, skip silently.
Re-read the updated CLAUDE.md fields after this step so the session resume report reflects the filled values.
Step 3 — Read project memory
Read .claude/memory/project.md.
Extract:
- The content of the most recent
## Checkpoint [...]block (3 bullets max) - Any entries under
## Active Conventions - Any entries under
## Technical Debt
If the file is absent or has no ## Checkpoint block, note "No checkpoints yet".
Step 4 — Read personal preferences
Read .claude/memory/personal.md. Extract developer preferences (verbosity, shortcuts, habits).
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.
- 4d ago First seen · 143 lines · 14 tokens per session scan A 9dd52caf5bbb
cc-resume is a command published in the GitHub repository yeisonrestrepo/code-conductor (6 stars, last pushed 1mo ago), licensed MIT. It adds 14 tokens to every session and 1,322 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
handoff
Fast session handover — capture current state and write a resume command for the next session. Use when context is filling up or you need to switch tasks.
learn
Persist a single insight, decision, or constraint to long-term memory with auto-classified category and tags.
wrap-up
End-of-session protocol — capture decisions, constraints, learnings, and next-session task; create a session snapshot before context is lost.
retrieve
Full-text search persistent memory (BM25) and present results grouped by category — decisions, constraints, learnings, tasks.
unwrap
You are resuming a Claude Code session. Execute all steps below in order — no confirmation needed.
wrap-find
Search session logs for a keyword or phrase. The search term is everything after /wrap-find in the user's message.