A command that saves project context, discoveries, decisions, and progress so they can be used in a later session. It can also create checkpoints, which are recovery points for ongoing work.

Use it when finishing a session, preserving project knowledge, recording lessons learned, or creating a checkpoint during complex work.

It reduces the need to rediscover how a project works after ending and restarting a coding session.

save — Command for Claude Code by SuperClaude-Org

About the project

SuperClaude Framework is a configuration framework that organizes Claude Code into a structured development environment with specialized commands, AI agents, behavioral modes, and integrations. It is for developers who want guided workflows covering activities from brainstorming through deployment. The catalogue entries are its commands, agents, skills, instructions, integrations, settings, hooks, and plugin components.

SuperClaude-Org/SuperClaude_Framework · 23,905 stars · on GitHub · superclaude.netlify.app

Install

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.

Clone the repo

git clone --depth 1 https://github.com/SuperClaude-Org/SuperClaude_Framework

Made for: Claude Code.

Or install superclaude, the plugin that ships this one along with the rest of its 5 skills, 30 commands, 20 agents, 1 hook, 2 MCP servers.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/commands/superclaude-org/superclaude_framework/save/github.svg)](https://agentmods.dev/commands/superclaude-org/superclaude_framework/save)

Your own site

<a href="https://agentmods.dev/commands/superclaude-org/superclaude_framework/save"><img src="https://agentmods.dev/badge/commands/superclaude-org/superclaude_framework/save/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/superclaude-org/superclaude_framework/save"><img src="https://agentmods.dev/badge/commands/superclaude-org/superclaude_framework/save.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 688 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00013	$0.00688
Opus 5.5	$0.00005	$0.00275
Sonnet 5.5	$0.00003	$0.00138
Haiku 4.5	$0.00001	$0.00069

Measured 1mo ago against content hash 15a5e9b6e11b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

save — 100% identical, 12 lines differ

plugins/superclaude/commands/save.md · 93 lines

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: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: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

Read the full file on GitHub · 93 lines

Changes

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 · 93 lines · 13 tokens per session scan A 15a5e9b6e11b

Subscribe to this mod's changes

save is a command published in the GitHub repository SuperClaude-Org/SuperClaude_Framework (23,905 stars, last pushed 20d ago), licensed MIT. It adds 13 tokens to every session and 688 once invoked, about $0.0001 per session on Opus 5.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-30.

Memory and context session

save