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.
git 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-checkpoint)<a href="https://agentmods.dev/commands/yeisonrestrepo/code-conductor/cc-checkpoint"><img src="https://agentmods.dev/badge/commands/yeisonrestrepo/code-conductor/cc-checkpoint/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.
<a href="https://agentmods.dev/commands/yeisonrestrepo/code-conductor/cc-checkpoint"><img src="https://agentmods.dev/badge/commands/yeisonrestrepo/code-conductor/cc-checkpoint.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00014 | $0.01757 |
| Opus 5.5 | $0.00006 | $0.00703 |
| Sonnet 5.5 | $0.00003 | $0.00351 |
| Haiku 4.5 | $0.00001 | $0.00176 |
Grade A, and why
cc-checkpoint 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 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.
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.
How it starts
The opening of the file, as written. The whole thing — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Read the conversation history from the current session.
Identify and extract:
- Decisions made — architectural choices, approach selections, rejected alternatives
- Conventions established — naming patterns, file organization, code style choices
- Technical debt — shortcuts taken, known limitations, deferred work
- Workarounds — non-obvious solutions and why they were needed
Update .claude/memory/project.md (append only, never delete):
- Add a timestamped section:
## Checkpoint [YYYY-MM-DD HH:MM] - List decisions, conventions, and debt from this session
Then update its ## Current State section, the bounded digest at the top of project.md that phase commands read with a limit instead of the whole file:
- If the section is absent, make the one-time bootstrap insert: add this skeleton directly after the file's
# Project Memoryintro paragraph, in one Edit. It inserts a new section and never rewrites an existing line, so it keeps the BUG-003 invariant.
## Current State
<!-- Bounded digest, max 40 lines, each line max 200 characters. History below is append-only. -->
- Active spec: none
- Last checkpoint: none
### Conventions
### Debt
<!-- end current state -->
- Replace the single
- Last checkpoint:line with the heading text of the entry just appended, without its leading##. - Add each new convention as a bullet under
### Conventionsand each new debt item or workaround as a bullet under### Debt, one Edit per bullet. - Caps: the section stays within 40 lines, each list within 12 bullets, each line within 200 characters. Before adding to a full list, remove the one bullet that is superseded or resolved, in its own Edit. A removed or shortened bullet loses nothing: the history entry holds the full text.
- If the
<!-- end current state -->line is missing, report the malformed section and leave it as it is. Never rewrite it in bulk.
Staging that update, where the workflow commits it: stage by tracked-ness, with an explicit path. A project.md that is already tracked takes git add -u ".claude/memory/project.md"; one that is not yet tracked takes plain git add ".claude/memory/project.md", or git add -f where the project ignores .claude/. Never an unconditional -u here. This command is global and also runs in freshly scaffolded projects, which do not ignore .claude/ and whose project.md is not yet tracked: there -u exits 128 and would halt the checkpoint before its DB tail, trading a defect those projects never had for one they would.
Update .claude/memory/personal.md (local only):
- Add any developer preferences observed this session
Report:
- Timestamp of this checkpoint
- What was saved to project.md (2–3 bullets)
- What was saved to personal.md (1–2 bullets)
Suggest running /cc-checkpoint automatically: before /compact, after completing a feature, after any key architectural decision.
Fail-open DB tail (best-effort, synchronous)
Run only after the project.md append succeeded (authoritative). Any failure here is non-fatal — never block or revert the project.md update.
- Ensure
.conductor/exists (mkdir -p .conductor, best-effort); if that fails, skip the tail. - Derive
c— the full-40git rev-parse HEAD(lowercased,/^[0-9a-f]{7,40}$/,"0000000"fallback on non-zero/timeout/git-absent/format-mismatch; shelltimeoutonly if the binary exists). - Resolve the id:
id="$(node .claude/scripts/session-id.mjs 2>>.conductor/last-write.log)". - Derive
phby carry-forward: with a bounded ~5 s outer timeout (only iftimeoutexists;conductor-db's internal 2 sbusy_timeoutbounds real contention otherwise), runnode <probe-flags> .claude/scripts/conductor-db.mjs get-session "$id"; if it prints a row whosephaseis a non-empty enum member, reuse it. On no row, empty phase, DB unavailable, or timeout, default to"impl". - Set
prto the verbatim## Checkpoint …section body just appended toproject.md(the same in-context string) — soproject.mdand the snapshot'sprare byte-identical.pris always non-empty here, so the blob is always v2. - Project
d/xfrom that section (best-effort): match headings/^#{2,4}[ \t]+(.+?)[ \t]*$/; normalize the heading text by removing all*,_,`then.trim()+ lowercase; a heading containingdecisionorconventionopens adblock, one containingdebt,workaround, orlimitationopens anxblock. Thedset is tested first and wins (a heading matching both opens onedblock). The parent## Checkpoint …heading matches no keyword, so it opens no block and closes any open one. Within a block, bullet lines/^[ \t]*[-*][ \t]+(\S.*?)[ \t]*$/contribute their trimmed capture (line-based; continuation lines ignored — the full text survives inpr). If unstructured,d/xmay be empty (valid). - Defaults:
n=[],f=[],s= the active spec stem or"none". - Build the v2 blob: pipe
{ph, c, s, n, f, d, x, pr}on stdin tonode .claude/scripts/snap-build.mjs; capture its stdout. If it exits non-zero, skip the DB write (fail-open). - Write the rows (both argv double-quoted; blob on stdin; all output to the log):
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 Changed · +18 lines a053ad60c72b
- 29d ago Changed · +2 lines 32a67f2c58ae
- 1mo ago First seen · 51 lines · 14 tokens per session scan A b5f792b1f882
cc-checkpoint is a command published in the GitHub repository yeisonrestrepo/code-conductor (17 stars, last pushed today), licensed MIT. It adds 14 tokens to every session and 1,757 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.
Other commands, from other repositories
kiro-steering-custom
Command "kiro-steering-custom" from gotalab/cc-sdd, covering kiro custom steering creation, workflow, available templates, steering principles and tool guidance.
setup-context
Set up your Skill Memory — a pm-context.md every skill reads so outputs come back tailored to you.
report
Generate a project analytics report covering code quality, velocity, and health metrics.
explain
Explain a code file, function, or concept in clear, structured language.
env-setup
Set up environment configuration files from templates with validation.
debug-pod
Debug a failing or unhealthy Kubernetes pod by analyzing events, logs, and configuration.