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 skills/tobzh30/claude-project-bootstrap/checkpointnpx skills add toBzh30/Claude-Project-Bootstrap --skill checkpointgit clone --depth 1 https://github.com/toBzh30/Claude-Project-BootstrapWrote 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/tobzh30/claude-project-bootstrap/checkpoint)<a href="https://agentmods.dev/skills/tobzh30/claude-project-bootstrap/checkpoint"><img src="https://agentmods.dev/badge/skills/tobzh30/claude-project-bootstrap/checkpoint.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.1 | $0.00050 | $0.00384 |
| Opus 5 | $0.00025 | $0.00192 |
| Sonnet 5 | $0.00010 | $0.00077 |
| Haiku 4.5 | $0.00005 | $0.00038 |
Grade A, and why
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 6d 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.
What it actually says
Capture the current session as a resumable handover so a fresh session (after /clear) can pick up cold without undoing work.
Steps
-
Run
printf '%s-%s' "$(date +%Y-%m-%dT%H%M)" "$(openssl rand -hex 3)"to get a timestamp with a random suffix (e.g.2026-04-22T1717-a3f9c1) for the filename. -
Generate a summary covering these sections — keep the whole document under 400 words:
- Project: name, repo path, one-line description
- Accomplished: bullet list of what was done this session
- Current state: branch, uncommitted changes, open PRs, test status, anything a fresh session needs to know to not undo work
- Pending: numbered list of next actions with enough detail to resume cold (include specific commands, file paths, URLs where relevant)
- Environment: non-obvious setup that won't survive a shell restart (e.g. ssh-add, nvm, auth tokens, background processes)
-
Write the summary to
~/.claude/handovers/<timestamp>.md. -
Print exactly this (substituting the real timestamp):
Saved to ~/.claude/handovers/<timestamp>.md
After /clear, paste this to resume:
Read ~/.claude/handovers/<timestamp>.md and resume from where we left off
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.
- 6d ago First seen · 30 lines · 50 tokens per session scan A f122d933eb5e
checkpoint is a skill published in the GitHub repository toBzh30/Claude-Project-Bootstrap (3 stars, last pushed 1mo ago), licensed MIT. It adds 50 tokens to every session and 384 once invoked, about $0.0003 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-31.
Other skills, from other repositories
thought
Capture a surprising model answer as a thought entry. Synthesizes the last answer with context, saves as a granular file, and auto-updates the TLDR.
alive:session-history
Revive sessions (quick or heavy), browse, and search — 'what happened recently?', 'find the session where we discussed X', 'revive yesterday's session'. For single-session recall and multi-session browsing. If the human needs to merge multiple sessions into one working context or detect conflicts between parallel…
recall
Must be used at the start of any non-trivial task involving code changes, debugging, repo exploration, file inspection, or environment/tooling investigation to surface stored guidance before analysis or tool use.
cross-session-handoff
Read, write, snapshot, and lock .arcgentic/state.yaml across planner, dev, audit, and optional test sessions.
knowledge-priming-refiner
Facilitate a structured conversation to create a project-specific knowledge base document. Produces a knowledge-base.md that primes AI with the project's tech stack, architecture, trusted sources, and project structure. Use when the user says 'set up knowledge base', 'prime the project', 'onboard AI', 'create…
alive-people
Weekly -- cross-reference people mentions, nudge stale contacts.