Borrowing it
Nothing to install: this file belongs to DeL-TaiseiOzaki/claude-code-orchestra. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/DeL-TaiseiOzaki/claude-code-orchestra/main/.claude/skills/checkpointing/SKILL.mdgit clone --depth 1 https://github.com/DeL-TaiseiOzaki/claude-code-orchestraWrote 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/skills/del-taiseiozaki/claude-code-orchestra/checkpointing)<a href="https://agentmods.dev/skills/del-taiseiozaki/claude-code-orchestra/checkpointing"><img src="https://agentmods.dev/badge/skills/del-taiseiozaki/claude-code-orchestra/checkpointing/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/skills/del-taiseiozaki/claude-code-orchestra/checkpointing"><img src="https://agentmods.dev/badge/skills/del-taiseiozaki/claude-code-orchestra/checkpointing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00026 | $0.01794 |
| Opus 5 | $0.00013 | $0.00897 |
| Sonnet 5 | $0.00005 | $0.00359 |
| Haiku 4.5 | $0.00003 | $0.00179 |
Grade A, and why
checkpointing 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 5d 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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Checkpointing
Capture durable session context without growing the always-loaded root
CLAUDE.md. Canonical state and artifacts live under .claude/.
Owned Paths
.claude/checkpoints/: full timestamped checkpoints; never deleted by the compact phase..claude/checkpoints/INDEX.md: generated catalog of every checkpoint.PROGRESS.md: latest five checkpoint summaries..claude/STATE.md: one Progress Tracker link and current working blocks..claude/logs/: drafts, previews, work logs, and CLI activity..claude/docs/research/: research notes; inactive notes may be archived only after user approval.
Both scripts write nothing without --apply. Every default run produces preview
files under .claude/logs/ and leaves PROGRESS.md and .claude/STATE.md
untouched.
Full Checkpoint
-
Determine the time window from the newest checkpoint, or use all available history when none exists.
-
Gather the user requests and decisions from the current conversation, git changes, CLI logs, team work logs, and relevant design changes.
-
Write a Japanese five-part summary containing:
何をしたのか,どういうやり取りをユーザーと行ったのか,どうやったのか,途中でどういう課題が起こったのか, and将来のアクション. This is the irreducible judgment in the skill and is never generated: a missing, empty, stale, or incomplete summary aborts the run with exit2. -
Save the summary to
.claude/logs/pending-summary.md, then preview:python3 .claude/skills/checkpointing/checkpoint.py \ --summary-file .claude/logs/pending-summary.mdExit
0reportsresult: previewand four preview files (checkpoint-preview-*,index-preview-*,progress-preview-*,state-preview-*under.claude/logs/). Exit1is a bad--since/--now; exit2is a summary or shared-state contract violation; exit3is a timestamp collision, a concurrent modification, or a write failure.Add
--label <slug>when the session's commit messages would not name it well; the label becomes the checkpoint's slug in the frontmatter and the index. -
Review the four previews, then write for real:
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 5d ago Changed · +1 tokens per session 73b647064139
- 6d ago Changed · +28 lines 4fa1f00b2a2d
- 10d ago First seen · 139 lines · 25 tokens per session scan A af08c2b1b6ce
checkpointing is a skill published in the GitHub repository DeL-TaiseiOzaki/claude-code-orchestra (194 stars, last pushed 6d ago), licensed MIT. It adds 26 tokens to every session and 1,794 once invoked, about $0.0001 per session on Opus 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-30.
Other skills, from other repositories
orbit-notion
Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
peekaboo
Capture and automate macOS UI with the Peekaboo CLI.
mochi-remind
Handle due reminders — notify the user with natural language and mark them done.