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/alivecontext/alive/session-historynpx skills add alivecontext/alive --skill session-historygit clone --depth 1 https://github.com/alivecontext/aliveWrote 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/alivecontext/alive/session-history)<a href="https://agentmods.dev/skills/alivecontext/alive/session-history"><img src="https://agentmods.dev/badge/skills/alivecontext/alive/session-history.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.00076 | $0.03171 |
| Opus 5 | $0.00038 | $0.01586 |
| Sonnet 5 | $0.00015 | $0.00634 |
| Haiku 4.5 | $0.00008 | $0.00317 |
Grade A, and why
alive:session-history 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 — 319 lines — stays where its author put it; the contents beside it link to each section on GitHub.
History
Session timeline and recent activity. The system's short-term memory.
Not a search (that's find — searches content across walnuts). History searches SESSIONS — what squirrels did, what was discussed, what was decided. For deep context extraction from source material, use alive:mine-for-context.
How It Works
Two tiers of data. Always start with tier 1. Go to tier 2 via revive.
Tier 1 — Squirrel Entries (.alive/_squirrels/*.yaml, with fallback to per-walnut _kernel/_squirrels/*.yaml)
Structured, fast, indexed. Session ID, walnut, model, timestamps, stash items, transcript path. Every squirrel leaves one of these.
Tier 2 — Session Transcripts (path stored in squirrel YAML transcript:)
The full conversation. Every message, every agent response, every tool call, every result. This is the deep context — the actual thinking, the back-and-forth, the nuance that didn't make it into the stash.
Modes
Browse (no args)
Show recent sessions across all walnuts. Default filter: only show sessions with saves > 0 or non-empty stash. Cap at 10 results. Add a summary line: "N empty shells not shown." Use history --shells to include them.
Data source: prefer .alive/_index.yaml recent_sessions: as primary data. Fall back to direct .alive/_squirrels/ YAML walk only if the index is missing or returns fewer results than requested.
╭─ squirrel history — recent sessions
│
│ 1. 2a8c95e9 nova-station today opus-4-6
│ System architecture, telemetry pipeline, 8 modules configured, shipped v0.1-beta
│
│ 2. a44d04aa nova-station yesterday opus-4-6
│ Supply chain mapped, vendor shortlist locked, timeline set
│
│ 3. 5551126e nova-station Feb 22 opus-4-6
│ Companion app, test harness, integration v0.1-beta released
│
│ 4. fb6ec273 nova-station Feb 21 opus-4-6
│ Transcript extraction, dashboard built, requirements captured
│
│ 5. 224e54bb stellarforge Feb 22 opus-4-6
│ stellarforge infrastructure, telemetry, comms, access system
│
│ number to dive in, or describe what you're looking for.
╰─
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 319 lines · 76 tokens per session scan A 78f3375a9cac
alive:session-history is a skill published in the GitHub repository alivecontext/alive (127 stars, last pushed 9d ago), licensed MIT. It adds 76 tokens to every session and 3,171 once invoked, about $0.0004 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
cco-overhead
Audit the fixed context overhead every session starts with — system prompt, MCP tools, agents, CLAUDE.md, memory — measured from real transcript usage.
handoff
Create a session briefing for the next session — auto-loaded, then archived. Use when the user is wrapping up a session, says "save this for next time", "hand off", "brief the next session", or wants to ensure continuity before stopping work.
forget
Remove entries from remembered items. Use when the user wants to delete, remove, or clear a previously remembered item, or says "forget this", "remove that memory", or "clear my preferences".
recall
Inject filtered context from previous sessions. Use when the user says "recall", "what happened last session", "what did we work on", "inject previous context", or when you need context from a prior session to continue work. Also useful mid-session when the user references prior work you don't have context for.
remember
Save something to memory for future sessions. Use when the user says "remember this", "save for later", "don't forget", or wants to persist any preference, fact, lesson, or note across sessions.
status
Check plugin health and diagnose issues. Use when the user asks about mneme health, memory status, plugin errors, wants to troubleshoot memory issues, or sees error warnings at session start.