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 skills/florianbruniaux/claude-code-plugins/session-savenpx skills add FlorianBruniaux/claude-code-plugins --skill session-savegit clone --depth 1 https://github.com/FlorianBruniaux/claude-code-pluginsWrote 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/skills/florianbruniaux/claude-code-plugins/session-save)<a href="https://agentmods.dev/skills/florianbruniaux/claude-code-plugins/session-save"><img src="https://agentmods.dev/badge/skills/florianbruniaux/claude-code-plugins/session-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.00031 | $0.00845 |
| Opus 5 | $0.00015 | $0.00423 |
| Sonnet 5 | $0.00006 | $0.00169 |
| Haiku 4.5 | $0.00003 | $0.00085 |
Grade A, and why
session-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 today.
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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/session-save
Capture the current session into a structured handoff file so you (or another instance) can resume with full context. Creates a timestamped Markdown file in .claude/sessions/.
When to Use
- Before ending a session that isn't complete
- Before switching to a different task
- Before context reaches 75%+ (to preserve the important parts)
- At natural milestones in a long task (after each phase)
- To hand off to a second Claude instance
Instructions
Produce a handoff document with the following structure:
Session Handoff: [TIMESTAMP]
What Was Being Done
[One paragraph: the goal, the approach, where things stand right now]
Files Modified This Session
[List every file that was created, edited, or deleted, with the nature of the change]
path/to/file.ts - [what changed and why]
path/to/other.ts - [what changed and why]
Key Decisions Made
[Architectural choices, tradeoffs accepted, approaches rejected and why]
- Decision: [What was decided]
- Rationale: [Why]
- Alternatives rejected: [What else was considered]
Current Status
[Where things are right now: what's working, what's broken, what's in-progress]
- Working: [...]
- In-progress: [...]
- Known issues: [...]
Next Steps (Ordered)
[The exact next actions to take to continue, specific enough that a fresh context can pick up without re-reading everything]
- [First action]:
path/to/file.ts- [what to do] - [...]
Context to Reload
[Files that must be read to resume with full understanding, keep this list short]
path/to/key-file.ts: [why it matters]CLAUDE.md: project rules
Blockers / Open Questions
[Anything unresolved that needs a decision or external input before proceeding]
- [Question or blocker]: [who/what can resolve it]
Implementation
Save the handoff to .claude/sessions/handoff-[YYYY-MM-DD-HHMM].md. Then output the file path so the user knows where to find it.
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.
- today First seen · 116 lines · 31 tokens per session scan A 9b1474d5ba7d
session-save is a skill published in the GitHub repository FlorianBruniaux/claude-code-plugins (40 stars, last pushed 3d ago), licensed MIT. It adds 31 tokens to every session and 845 once invoked, about $0.0002 per session on Opus 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-09-04.
Other skills, from other repositories
vc-autopilot
Emit and validate the provisional goal block for Autopilot Mode. Owns the 9-field format and resume detection from a pasted goal block.
vc-problem-solving
Apply systematic problem-solving techniques when stuck. Use for complexity spirals, innovation blocks, recurring patterns, assumption constraints, simplification cascades, scale uncertainty.
thoroughness-scoring
Score every decision point with a Thoroughness Rating (1-10). AI makes the marginal cost of doing things properly near-zero — pick the higher-rated option every time. Includes scope checks to distinguish contained vs unbounded work.
report
Read the delivery log and say which rules actually fire, which never have, and what to prune or fix. Use when the user asks whether ballast is doing anything, wants to clean up their rule catalog, or on a periodic review.
orchestrate
Wire Commands, Agents, and Skills together for complex features. Use when building features that need research, planning, and implementation phases.
squid-self-improve
Analyze developer corrections from the current coding session and persist lessons learned as rules in AGENTS.md files or memory. Use at the end of a session after the developer corrected your work, when they say "squid-self-improve", ask to capture what was learned, or ask you to reflect on mistakes and extract…