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/superclaude-org/superclaude_plugin/sc-savegit clone --depth 1 https://github.com/SuperClaude-Org/SuperClaude_PluginWrote 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/superclaude-org/superclaude_plugin/sc-save)<a href="https://agentmods.dev/commands/superclaude-org/superclaude_plugin/sc-save"><img src="https://agentmods.dev/badge/commands/superclaude-org/superclaude_plugin/sc-save.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.00013 | $0.00702 |
| Opus 5 | $0.00006 | $0.00351 |
| Sonnet 5 | $0.00003 | $0.00140 |
| Haiku 4.5 | $0.00001 | $0.00070 |
Grade A, and why
save 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.
This is a copy
100% identical to save — 12 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/sc:sc:sc:save - Session Context Persistence
Triggers
- Session completion and project context persistence needs
- Cross-session memory management and checkpoint creation requests
- Project understanding preservation and discovery archival scenarios
- Session lifecycle management and progress tracking requirements
Usage
/sc:sc:save [--type session|learnings|context|all] [--summarize] [--checkpoint]
Behavioral Flow
- Analyze: Examine session progress and identify discoveries worth preserving
- Persist: Save session context and learnings using Serena MCP memory management
- Checkpoint: Create recovery points for complex sessions and progress tracking
- Validate: Ensure session data integrity and cross-session compatibility
- Prepare: Ready session context for seamless continuation in future sessions
Key behaviors:
- Serena MCP integration for memory management and cross-session persistence
- Automatic checkpoint creation based on session progress and critical tasks
- Session context preservation with comprehensive discovery and pattern archival
- Cross-session learning with accumulated project insights and technical decisions
MCP Integration
- Serena MCP: Mandatory integration for session management, memory operations, and cross-session persistence
- Memory Operations: Session context storage, checkpoint creation, and discovery archival
- Performance Critical: <200ms for memory operations, <1s for checkpoint creation
Tool Coordination
- write_memory/read_memory: Core session context persistence and retrieval
- think_about_collected_information: Session analysis and discovery identification
- summarize_changes: Session summary generation and progress documentation
- TodoRead: Task completion tracking for automatic checkpoint triggers
Key Patterns
- Session Preservation: Discovery analysis → memory persistence → checkpoint creation
- Cross-Session Learning: Context accumulation → pattern archival → enhanced project understanding
- Progress Tracking: Task completion → automatic checkpoints → session continuity
- Recovery Planning: State preservation → checkpoint validation → restoration readiness
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 · 93 lines · 13 tokens per session scan A d360a611050f
save is a command published in the GitHub repository SuperClaude-Org/SuperClaude_Plugin (55 stars, last pushed 13d ago), licensed MIT. It adds 13 tokens to every session and 702 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to save, differing in 12 lines, and is treated as a copy.
Other commands, from other repositories
AI: Handoff
Generate a HANDOFF.md snapshot of session state for cross-session continuity.
load
Session lifecycle management with Serena MCP integration for project context loading.
save
Session lifecycle management with Serena MCP integration for session context persistence.
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.