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 faizkhairi/claude-code-blueprint --skill save-sessiongit clone --depth 1 https://github.com/faizkhairi/claude-code-blueprintWrote 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/faizkhairi/claude-code-blueprint/save-session)<a href="https://agentmods.dev/skills/faizkhairi/claude-code-blueprint/save-session"><img src="https://agentmods.dev/badge/skills/faizkhairi/claude-code-blueprint/save-session/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/faizkhairi/claude-code-blueprint/save-session"><img src="https://agentmods.dev/badge/skills/faizkhairi/claude-code-blueprint/save-session.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00076 | $0.00619 |
| Opus 5.5 | $0.00030 | $0.00248 |
| Sonnet 5.5 | $0.00015 | $0.00124 |
| Haiku 4.5 | $0.00008 | $0.00062 |
Grade A, and why
save-session 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 2mo 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
Prerequisite check (run first): if ./memory/ does not exist OR ~/.claude/.memory-disabled marker file is present, this skill is a no-op. Output: "Memory persistence is disabled. Run ./setup.sh and choose to enable memory if you want this skill to work."
Save session state to memory:
-
Update session.md at
./memory/core/session.md:- Current topic and what we're working on
- Recent progress (what was accomplished this session)
- Next steps (what should happen next session)
- Any blockers or open questions
-
Update reminders at
./memory/core/reminders.md:- Ask the user if there are any pending tasks, deadlines, or reminders to carry forward
- Remove completed reminders (move to Completed section with date), keep active ones, add new ones
-
Update per-project context: If working on a registered project, update
./memory/projects/active/{project}.md→ Session Context section:- Last worked on (what specifically)
- In progress (current state)
- Next up (what should happen next on THIS project)
-
Check preferences.md: If new preferences or work patterns were observed during this session, update
./memory/core/preferences.md -
Check MEMORY.md: If new technical learnings or gotchas were discovered, update
{MEMORY_MD_PATH}. After any edit, count total lines; if over 170, warn that MEMORY.md is approaching the 200-line auto-truncation limit and suggest moving content to topic files. -
Check decisions.md: If a non-obvious architectural or technical decision was made this session (something future-us would ask "why?"), append to
./memory/core/decisions.mdusing the existing format:## YYYY-MM-DD: Title/**Context**/**Decision**/**Rationale** -
Diary (if this was a significant session, e.g., feature shipped, major bug fixed, architecture decision made): Use the
save-diaryskill to create or append an entry to./memory/diary/current/YYYY-MM-DD.md -
Git commit + push memory: Stage all changed files in memory, commit with a descriptive message, and push to GitHub (
git push origin main). This keeps the remote diary and session state up to date. -
Confirm: Summarize what was saved and where
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.
- 2mo ago First seen · 37 lines · 76 tokens per session scan A 74fb63fe582a
save-session is a skill published in the GitHub repository faizkhairi/claude-code-blueprint (73 stars, last pushed 1mo ago), licensed MIT. It adds 76 tokens to every session and 619 once invoked, about $0.0003 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.
Other skills, from other repositories
ctx
Use ctx as working memory for prior agent work. Before starting or continuing work in an unfamiliar area, resuming earlier work, or revisiting an investigation, search prior sessions to ground yourself in earlier context. Use ctx blame to trace a line, file, commit, or PR to the agent session that produced it. Use…
semantix
Install and use the semantix memory kernel as a middleware in your agent: extract user preferences / workflows / experience from past sessions, retrieve and inject them on demand. One binary + your agent's own tools.
save-progress
Save current project task progress to local task state file for cross-session continuity. Use when the user asks to save progress, uses an equivalent localized trigger phrase, the session is interrupted, or the user wants to resume work later. Writes to .claude/project-task-state.json so next session can load it via…
memorix-memory
Use when prior workspace context, past decisions, solved bugs, handoff state, or durable project knowledge would help a coding task.
memorix
Use when Claude Code needs Memorix shared memory, reasoning, Git Memory, mini-skills, session handoff, orchestration coordination, or integration troubleshooting.
memorix-mini-skills
Use when durable project knowledge, gotchas, workflows, or repeated fixes should become reusable agent guidance instead of ordinary memory.