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/superpitt/self-improving-memory-mcp/checkpointgit clone --depth 1 https://github.com/SuperPiTT/self-improving-memory-mcpWhat 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.00441 |
| Opus 5 | $0.00000 | $0.00220 |
| Sonnet 5 | $0.00000 | $0.00088 |
| Haiku 4.5 | $0.00000 | $0.00044 |
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 2d 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
Manual Checkpoint Command
Save current conversation state to memory before it gets too long or you need to pause work.
Usage
/checkpoint [optional-description]
What this does
This command triggers the Pre-Compact Interceptor Agent manually to:
-
Capture complete session state
- Everything discussed and decided
- All files modified
- Pending tasks
- Key context and decisions
-
Save to memory
- Creates checkpoint entity in knowledge base
- Links to all related work
- Preserves TodoWrite state
-
Generate continuation summary
- Compact summary to copy/paste
- Resume instructions
- All context preserved
When to use
- Before taking a break
- When context is getting long (check token count)
- Before starting risky/complex work
- At natural breakpoints (milestone completed)
- When you want to continue later in fresh conversation
Example
/checkpoint before implementing authentication
After checkpoint
You'll receive:
- Confirmation that state is saved
- A continuation summary to copy
- Instructions to start fresh conversation
To resume later
In a NEW conversation, paste the continuation summary and Context Recovery Agent will automatically load the full context from memory.
Now activating Pre-Compact Interceptor Agent...
You are the Pre-Compact Interceptor Agent.
The user has manually triggered a checkpoint. Follow your instructions in .claude/agents/pre-compact-interceptor.md:
- Capture complete current session state
- Create comprehensive checkpoint entity
- Save to memory with all context
- Generate continuation summary
- Provide clear resume instructions
Additional context from command:
- Manual trigger: yes
- User description: "{{ARGS}}" (if provided)
- Treat this as high-priority checkpoint
Begin checkpoint process now.
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.
- 2d ago First seen · 85 lines · 0 tokens per session scan A 2f83eae8f398
checkpoint is a command published in the GitHub repository SuperPiTT/self-improving-memory-mcp (0 stars, last pushed 11mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 441 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-09-01.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.