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 commands/lesleslie/session-buddy/session-buddy-checkpointgit clone --depth 1 https://github.com/lesleslie/session-buddyWrote 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/lesleslie/session-buddy/session-buddy-checkpoint)<a href="https://agentmods.dev/commands/lesleslie/session-buddy/session-buddy-checkpoint"><img src="https://agentmods.dev/badge/commands/lesleslie/session-buddy/session-buddy-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 | $0.00000 | $0.00334 |
| Opus 5 | $0.00000 | $0.00167 |
| Sonnet 5 | $0.00000 | $0.00067 |
| Haiku 4.5 | $0.00000 | $0.00033 |
Grade A, and why
session-buddy-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.
What it actually says
status: active role: canonical date: 2026-07-16 last_reviewed: 2026-07-16 superseded_by: null blocks_on: [] topic: plugin-standardization
argument-hint:
- checkpoint-name description: Create a session checkpoint with progress summary id: 01K6GZZRTDXPTKXJ5YMF07CK2H
Use the mcp__session-buddy__checkpoint tool to create a session checkpoint.
This command will:
- Create a checkpoint of the current development session
- Analyze code quality and calculate quality scores
- Summarize progress made so far
- Document any pending tasks or context
- Prepare for seamless session resumption
The tool will analyze the working directory and provide comprehensive quality metrics.
Notes-as-Memory Format
When creating checkpoint summaries, use structured notes instead of full conversation replay. This reduces token usage by ~90% while preserving essential context:
## Checkpoint Notes
- **Decision**: [What was decided and which option was chosen]
- **Reason**: [Why — the constraint, tradeoff, or requirement that drove the choice]
- **Files changed**: [exact/path/to/file.py (created|modified), ...]
- **Next step**: [The single next action after this checkpoint]
- **Blockers**: [None | description of what is blocking progress]
Do not replay the full conversation. Do not summarize what was discussed. Only record decisions, reasons, files, and next steps.
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 First seen · 42 lines · 0 tokens per session scan A 46f5716085a6
session-buddy-checkpoint is a command published in the GitHub repository lesleslie/session-buddy (2 stars, last pushed 4d ago), licensed BSD-3-Clause. It costs nothing until one of its globs matches a file; then it loads 334 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
minutes-ideas
Surface recent voice memos and ideas captured from any device. Use when the user asks "what ideas did I have?", "what were my recent memos?", "what did I record while walking?", or wants to recall a captured thought.
learn
Force claude-smart to extract learnings from this session now.
session-end
I'll summarize this coding session and update the memory system with our accomplishments.
memory-store
Store an insight, decision, or pattern to memory.
analyze-context
USE WHEN you want to analyze project context before starting work on a task. Calls context + recall, then synthesizes goals, decisions, gotchas, and relevant memories into a pre-task brief.
cc-memory
Configure persistent memory that survives across sessions using a layered approach: split rule files for always-loaded context, auto-memory for organic learning, and optional MCP-backed long-term memory for large codebases.