Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add unclecode/claude-code-tools/plugin install unclecode-cc-toolkitWrote 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/unclecode/claude-code-tools/pp-checkpoint)<a href="https://agentmods.dev/commands/unclecode/claude-code-tools/pp-checkpoint"><img src="https://agentmods.dev/badge/commands/unclecode/claude-code-tools/pp-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/unclecode/claude-code-tools/pp-checkpoint"><img src="https://agentmods.dev/badge/commands/unclecode/claude-code-tools/pp-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.00000 | $0.01666 |
| Opus 5.5 | $0.00000 | $0.00666 |
| Sonnet 5.5 | $0.00000 | $0.00333 |
| Haiku 4.5 | $0.00000 | $0.00167 |
Grade A, and why
pp-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 1mo 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 — 248 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Save Session Checkpoint
Save current chat session state and prepare instructions for next session.
Arguments
$ARGUMENTS
Optional query to add extra guidance for the next session. This query will be incorporated into the "What To Do Next" section of NEXT.md.
Examples:
/pp-checkpoint focus on fixing the auth bug first/pp-checkpoint user will provide new API docs tomorrow/pp-checkpoint skip T260, move directly to T262
Purpose
Called at the end of a chat session (or before hitting token limits) to:
- Create compact summary of current session (history file)
- Save comprehensive "what to do next" instructions (NEXT.md)
- Optionally create AI-compressed dump of chat history
- Link to full chat transcript
Execution Instructions
Step 1: Identify Current Session
# Get current working directory
pwd
# Convert to Claude projects path
# Example: /Users/unclecode/devs/project
# Becomes: ~/.claude/projects/-Users-unclecode-devs-project/
# Find most recent .jsonl file (exclude agent-* files)
ls -lt ~/.claude/projects/-Users-unclecode-devs-{converted-path}/*.jsonl | grep -v "agent-" | head -1
# Extract UUID from filename
# Example: 530170ff-52f5-4ad6-a333-22a09bd64773.jsonl
# UUID: 530170ff-52f5-4ad6-a333-22a09bd64773
Step 2: Determine Active Subproject
Read .context/project/INDEX.md to identify active subproject.
Step 3: Ask User About Chat History Dump
ALWAYS ask the user:
Before saving checkpoint, do you want me to create a compressed dump of this chat session?
This will use AI to compress the full conversation into a readable summary (~5-10% of original size) that captures all important details, decisions, and code changes.
Options:
1. **Yes** - Create compressed dump (takes ~30-60 seconds)
2. **No** - Skip dump, just save checkpoint files
Note: The raw .jsonl transcript is always available for grep/search regardless.
If user says Yes:
- Run the
/compress-chatcommand on the current session - Save compressed output to
.context/project/{active}/history/{uuid}-{YYYY-MM-DD}-dump.md
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.
- 1mo ago First seen · 248 lines · 0 tokens per session scan A c5921a0c7045
pp-checkpoint is a command published in the GitHub repository unclecode/claude-code-tools (4 stars, last pushed 10mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,666 tokens. 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
setup-context
Set up your Skill Memory — a pm-context.md every skill reads so outputs come back tailored to you.
brain
Set up or use your Professional Brain — init, ingest, recall, or review.
pull-learnings
Pulls shared organization patterns into local org-patterns.toon.
perf-difficult-conversation
Three-conversations framework rehearsal (Stone/Patton/Heen — Harvard Negotiation Project) for high-stakes conversations — termination, demotion, hard feedback, conflict surfacing. Produces three-conversations breakdown (what-happened / feelings / identity), conversation script with multiple opening choices, SCARF…
culture-onboarding-90
Design a 90-day onboarding architecture for a role. First day (psychological safety + belonging activation), first week (relationship + role context + early wins), first month (skill ramp + integration + baseline), first quarter (autonomous performance + cultural integration check). Written-first elements for…
reclaim-knowledge
Organize scattered professional material into a domain-based second-brain architecture. Maps existing sources (Canva, Drive, local folders, Notion, screenshots) to functional domains. Non-technical-friendly — produces folder structure + drag-and-drop instructions, not CLI commands.