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 commands/llcoolblaze/claude-boris/session-endgit clone --depth 1 https://github.com/llcoolblaze/claude-borisWrote 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/commands/llcoolblaze/claude-boris/session-end)<a href="https://agentmods.dev/commands/llcoolblaze/claude-boris/session-end"><img src="https://agentmods.dev/badge/commands/llcoolblaze/claude-boris/session-end.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.00018 | $0.00824 |
| Opus 5 | $0.00009 | $0.00412 |
| Sonnet 5 | $0.00004 | $0.00165 |
| Haiku 4.5 | $0.00002 | $0.00082 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Session End
Current State
Uncommitted Changes
!git status --short 2>/dev/null || echo "Not a git repo"
!git diff --stat 2>/dev/null | tail -10
Commits This Session
!git log --oneline --since="8 hours ago" 2>/dev/null | head -10
Files Modified Recently
!git diff --name-only HEAD~5 2>/dev/null | head -15 || echo ""
Session Wrap-up Protocol
1. Handle Uncommitted Work
If uncommitted changes exist:
Option A - Ready to commit:
# Verify first
/verify-all
# Then commit
/commit-push-pr
Option B - Work in progress:
# Create checkpoint
git stash push -m "session-end-$(date +%Y%m%d-%H%M%S)"
Option C - Save as WIP commit:
git add -A
git commit -m "wip: session checkpoint - [brief description]"
2. Generate Session Summary
Analyze this session and document:
What Was Accomplished
- List completed tasks
- Note features implemented
- Record bugs fixed
- Count commits made
Key Decisions Made
- Any architectural choices
- Technical trade-offs decided
- Patterns established
Files Modified
- List significant file changes
- Note new files created
- Flag deleted files
3. Update Memory Bank
Update .claude/memory/activeContext.md:
- Current working state
- Files in focus
- Open questions
- Next steps
Update .claude/memory/progress.md:
- Mark completed items as done
- Add newly discovered tasks
- Update in-progress items
Append to .claude/memory/sessionHistory.md:
## [Today's Date] [Time] - Session Summary
### Duration
[Approximate session length]
### What Was Accomplished
- [Task 1]
- [Task 2]
### Key Decisions Made
- [Decision if any]
### Files Modified
- `path/file.ts` - [change summary]
### Commits Created
- `SHA` message
### Context for Next Session
[Critical info the next Claude needs]
### Open Items
- [ ] [Unfinished work]
- [ ] [Questions to resolve]
Update .claude/memory/conventions.md (if learned something new):
- New patterns discovered
- Mistakes to avoid
- Best practices identified
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 · 170 lines · 18 tokens per session scan A 8967d6994b46
session-end is a command published in the GitHub repository llcoolblaze/claude-boris (48 stars, last pushed 7mo ago), licensed MIT. It adds 18 tokens to every session and 824 once invoked, about $0.0001 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 commands, from other repositories
minutes-ideas
Surface recent voice memos and ideas captured from any device. Use when the user asks "what ideas did I have?", "what were my recent memos?", "what did I record while walking?", or wants to recall a captured thought.
learn
Force claude-smart to extract learnings from this session now.
session-end
I'll summarize this coding session and update the memory system with our accomplishments.
memory-store
Store an insight, decision, or pattern to memory.
cc-memory
Configure persistent memory that survives across sessions using a layered approach: split rule files for always-loaded context, auto-memory for organic learning, and optional MCP-backed long-term memory for large codebases.
neo-review
Get Neo's code review with semantic matching against past findings in memory. Use on a diff or module before merge, especially where earlier mistakes in this codebase are likely to recur. Skip for formatting, lint-catchable issues, and single-line changes.