cc-checkpoint

cc-checkpoint is a command for Claude Code from yeisonrestrepo/code-conductor. It costs 14 tokens per session (1,757 once invoked), scanned A, original, MIT.

A command that records important decisions, coding conventions, technical debt, and workarounds from the current session in project memory files.

In plain words
What is it for?
Use it after major decisions, feature work, or before compacting a session to preserve project and developer preferences.
Why use it?
It prevents key context from being lost when a session is shortened, ended, or revisited later.

Command for Claude Code

Written for Claude Code: a Claude Code command (commands/*.md).

Good fit Use it after major decisions, feature work, or before compacting a session to preserve project and developer preferences.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/yeisonrestrepo/code-conductor/cc-checkpoint
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.

Clone the repo
git clone --depth 1 https://github.com/yeisonrestrepo/code-conductor

Made for: Claude Code.

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 cc-checkpoint

README.md
[![agentmods](https://agentmods.dev/badge/commands/yeisonrestrepo/code-conductor/cc-checkpoint/github.svg)](https://agentmods.dev/commands/yeisonrestrepo/code-conductor/cc-checkpoint)
Your own site
<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.

agentmods 80×15 button for cc-checkpoint

Your own site · 80×15
<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>
Per session 14 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,757 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.00014 $0.01757
Opus 5.5 $0.00006 $0.00703
Sonnet 5.5 $0.00003 $0.00351
Haiku 4.5 $0.00001 $0.00176

Measured 4d ago against content hash a053ad60c72b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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.

global/commands/cc-checkpoint.md · 71 lines

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:

  1. Decisions made — architectural choices, approach selections, rejected alternatives
  2. Conventions established — naming patterns, file organization, code style choices
  3. Technical debt — shortcuts taken, known limitations, deferred work
  4. 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 Memory intro 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 ### Conventions and 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.

  1. Ensure .conductor/ exists (mkdir -p .conductor, best-effort); if that fails, skip the tail.
  2. Derive c — the full-40 git rev-parse HEAD (lowercased, /^[0-9a-f]{7,40}$/, "0000000" fallback on non-zero/timeout/git-absent/format-mismatch; shell timeout only if the binary exists).
  3. Resolve the id: id="$(node .claude/scripts/session-id.mjs 2>>.conductor/last-write.log)".
  4. Derive ph by carry-forward: with a bounded ~5 s outer timeout (only if timeout exists; conductor-db's internal 2 s busy_timeout bounds real contention otherwise), run node <probe-flags> .claude/scripts/conductor-db.mjs get-session "$id"; if it prints a row whose phase is a non-empty enum member, reuse it. On no row, empty phase, DB unavailable, or timeout, default to "impl".
  5. Set pr to the verbatim ## Checkpoint … section body just appended to project.md (the same in-context string) — so project.md and the snapshot's pr are byte-identical. pr is always non-empty here, so the blob is always v2.
  6. Project d / x from that section (best-effort): match headings /^#{2,4}[ \t]+(.+?)[ \t]*$/; normalize the heading text by removing all *, _, ` then .trim() + lowercase; a heading containing decision or convention opens a d block, one containing debt, workaround, or limitation opens an x block. The d set is tested first and wins (a heading matching both opens one d block). 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 in pr). If unstructured, d/x may be empty (valid).
  7. Defaults: n=[], f=[], s= the active spec stem or "none".
  8. Build the v2 blob: pipe {ph, c, s, n, f, d, x, pr} on stdin to node .claude/scripts/snap-build.mjs; capture its stdout. If it exits non-zero, skip the DB write (fail-open).
  9. Write the rows (both argv double-quoted; blob on stdin; all output to the log):

Read the full file on GitHub · 71 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. 4d ago Changed · +18 lines a053ad60c72b
  2. 29d ago Changed · +2 lines 32a67f2c58ae
  3. 1mo ago First seen · 51 lines · 14 tokens per session scan A b5f792b1f882

Subscribe to this mod's changes

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.