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 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/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.
<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="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 108 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00031 | $0.00845 |
| Opus 5.5 | $0.00012 | $0.00338 |
| Sonnet 5.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 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.
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.
- 1mo ago 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 (42 stars, last pushed 1mo ago), licensed MIT. It adds 31 tokens to every session and 845 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-09-04.
Other skills, from other repositories
productivity
Personal productivity, time management, project management, team productivity, automation, and process improvement skills. GTD, time-blocking, focus systems, async workflows. Triggers on: productivity, time management, GTD, focus, deep work, async, project management, workflow, habits.
send-email
Compose and send a one-off email to a named recipient via Resend - written in the operator's voice, then sent in-run through the shared send caps with an operator audit copy.
caveman-help
Quick-reference card for all caveman modes, skills, and commands. One-shot display, not a persistent mode. Trigger: /caveman-help, "caveman help", "what caveman commands", "how do I use caveman".
get-started
First-run setup for the Aeon plugin. Checks the connection to the user's Aeon agent, shows what it can do, and runs one skill so the user sees it work. Use right after the plugin is installed, or when the user asks how to get started with Aeon.
toolbox
Pre/post dev toolbox — named bundles of skills/agents loaded before development work and councils of experts invoked after. Run /toolbox or the toolbox.py CLI to list, activate, initialize, export, import, and validate toolboxes. Invoke at the start or end of a dev session, when setting up a new repo, or when sharing…
low-code-platforms
Low-code and internal tool platforms including Retool, Supabase, Appsmith, Tooljet, n8n, and Zapier. Use when building admin panels, internal tools, workflow automations, or integrating low-code platforms with custom code.