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/imtylerrrrrr/second-brain/end-sessionnpx skills add Imtylerrrrrr/second-brain --skill end-sessiongit clone --depth 1 https://github.com/Imtylerrrrrr/second-brainWrote 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/imtylerrrrrr/second-brain/end-session)<a href="https://agentmods.dev/skills/imtylerrrrrr/second-brain/end-session"><img src="https://agentmods.dev/badge/skills/imtylerrrrrr/second-brain/end-session.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.00047 | $0.00547 |
| Opus 5 | $0.00023 | $0.00273 |
| Sonnet 5 | $0.00009 | $0.00109 |
| Haiku 4.5 | $0.00005 | $0.00055 |
Grade A, and why
end-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 4d 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
second-brain: end-session
Git-anchored write. Follow the discipline below EXACTLY — Part 1 governs this skill.
!cat "${CLAUDE_PLUGIN_ROOT}/references/discipline.md"
Steps
- Locate the vault (cwd or ancestors containing
Projects/Dashboard.md; else registered vaults in~/.claude/second-brain/vaults, ask if several; none → "run /second-brain:setup first"). - Which repo(s) were touched this session? Evidence: this conversation's work +
git -C <repo> status -sb+git -C <repo> log --oneline -10. Cannot tell → ASK the user; never guess. - For each touched repo, update
Projects/<repo>.mdper Part 1:## ▶ Thread→Last:cited facts — ALL commits since that note'slast_handoff_commit(hash+subject viagit log <last_handoff_commit>..HEAD --oneline, or the full log iflast_handoff_commit: none), not just commits made in this conversation turn; plus files changed, tests run, user decisions;Next:the user's stated intent (ask if unstated).- frontmatter →
last_handoff_commit: $(git -C <repo> rev-parse --short HEAD),branch,last_updated: today. ## 🕑 Session log→ prepend one dated line.- Milestone candidates → append
- [ ] confirm milestone "<name>" → /second-brain:analyze <repo>to## ✅ TODO. Do NOT touch milestone boxes.
- Update the Dashboard row for this repo only (Last session · Next · Updated). Row missing → add it.
- Sync L1:
bash "${CLAUDE_PLUGIN_ROOT}/scripts/sync.sh" - Git hygiene: uncommitted/untracked changes in touched repos → flag them ("commit before you forget?"). Never commit for the user unless asked.
- Confirm in one line per repo: what was recorded + the anchor hash.
Rules
- Facts cited, intent labeled, unknown → ask. NEVER check milestone boxes (that is /second-brain:analyze's job). No transcript summaries.
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.
- 4d ago First seen · 28 lines · 47 tokens per session scan A c0d957ffcb41
end-session is a skill published in the GitHub repository Imtylerrrrrr/second-brain (1 stars, last pushed 2mo ago), licensed MIT. It adds 47 tokens to every session and 547 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-08-31.
Other skills, from other repositories
s-continue
Cheaper and faster than /compact. Restores previous session context from Claude Code AND Codex transcripts by reading them directly — no LLM calls, no token cost. Also auto-loads a handoff written by /s-compact, if one exists. Triggers on "s-continue", "restore context", "what was I doing", "pick up where I left off"…
handoff-more
Pull older handoffs from .claude/handoffhistory/ into the current session's context. Requires the scripts/hooks installed by this repo's ./install.sh — the history it reads only exists once those are in place. Use when the auto-loaded handoffcurrent.md is thin (placeholder Notes, missing context the user is…
handoff
Snapshot session state to .claude/handoffcurrent.md and tell the user (loudly, with --- borders) to start a new session. Requires the scripts/hooks installed by this repo's ./install.sh — not a prompt-only skill. Use at clean boundaries (commit lands, track wraps), when the user signals context pressure ("getting…
setup
Scaffold the handoff project-memory system into THIS repository (new or existing) — copies the template tree into .handoff/, then runs a guided discovery pass that drafts a real STATUS, MAP, TECHSTACK, and PRODUCT from the actual codebase and confirms with the user before saving. Use when the user says "set up…
memory-recall
Search and recall relevant memories from past sessions via memsearch. Use when the user's question could benefit from historical context, past decisions, debugging notes, previous conversations, or project knowledge -- especially questions like 'what did I decide about X', 'why did we do Y', or 'have I seen this…
alive:session-history
Revive sessions (quick or heavy), browse, and search — 'what happened recently?', 'find the session where we discussed X', 'revive yesterday's session'. For single-session recall and multi-session browsing. If the human needs to merge multiple sessions into one working context or detect conflicts between parallel…