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 session-endgit 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/session-end)<a href="https://agentmods.dev/skills/faizkhairi/claude-code-blueprint/session-end"><img src="https://agentmods.dev/badge/skills/faizkhairi/claude-code-blueprint/session-end.svg" alt="Measured on agentmods" 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.00107 | $0.00941 |
| Opus 5 | $0.00053 | $0.00470 |
| Sonnet 5 | $0.00021 | $0.00188 |
| Haiku 4.5 | $0.00011 | $0.00094 |
Grade A, and why
session-end 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 7d 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 — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prerequisite check (run first): if ./memory/ does not exist OR ~/.claude/.memory-disabled marker file is present, skip the save-session/save-diary steps but still acknowledge the user's farewell. Output: "Memory persistence is disabled, see you next time." Otherwise proceed with the full wrap-up below.
Session End: Graceful Wrap-Up
Runs both save-session and save-diary together as one clean session close.
Activation
When this skill activates, output: "Wrapping up, saving session and diary."
Step 1: Save Session Context
Update ./memory/core/session.md:
- Last session summary: What was accomplished today (specific, not generic)
- Current working state: Where things stand, what's in-progress, what's done
- Next steps: What should be picked up next session
- Blockers or open questions: Anything left unresolved
Step 2: Update Reminders
Update ./memory/core/reminders.md:
- Ask the user: any pending tasks, deadlines, or reminders to carry forward?
- Move completed reminders to the Completed section with date
- Keep active ones, add new ones
Step 3: Update Per-Project Context
If working on a registered project, update ./memory/projects/active/{project}.md → Session Context section with what was last worked on, current state, and next steps for that project.
Step 4: Check for Memory Updates
- preferences.md: Were any new preferences, tools, or working patterns observed? Update
./memory/core/preferences.mdif so. - MEMORY.md: Were any new technical learnings, gotchas, or architectural decisions made? Update
{MEMORY_MD_PATH}if so. Size guard: after editing, count lines; warn if over 170 (200-line truncation limit). - decisions.md: Was a non-obvious architectural or technical decision made? Append to
./memory/core/decisions.mdusing format:## YYYY-MM-DD: Title/**Context**/**Decision**/**Rationale**
Step 5: Save Diary Entry (if session was significant)
A session is "significant" if any of these are true:
- Feature shipped or major bug fixed
- Architecture or tech decision made
- New project started or milestone reached
- Meaningful learning or discovery happened
- Career or profile work done
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.
- 7d ago First seen · 87 lines · 107 tokens per session scan A 5e8ebe0b2de3
session-end is a skill published in the GitHub repository faizkhairi/claude-code-blueprint (70 stars, last pushed 26d ago), licensed MIT. It adds 107 tokens to every session and 941 once invoked, about $0.0005 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-08-30.
Other skills, from other repositories
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.
memorix-git-memory
Use when the task depends on commit history, what changed, when a fix shipped, or linking engineering evidence to reasoning memory.