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 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/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/alivecontext/alive/session-history"><img src="https://agentmods.dev/badge/skills/alivecontext/alive/session-history.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 148 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.03171 |
| Opus 5.5 | $0.00030 | $0.01268 |
| Sonnet 5.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 1mo 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.
- 1mo 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 (130 stars, last pushed 17d ago), licensed MIT. It adds 76 tokens to every session and 3,171 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
doc-digest
Turn a long document, PDF, transcript, spreadsheet or log into a compact working digest the conversation can continue from. Use when the user shares or pastes something long (several pages or more) and wants to discuss, analyze, compare or use it over more than one message, or asks to summarize a document so they can…
fresh-start
Continue in a new chat without losing anything — writes a compact handoff to paste into a fresh conversation. Use whenever the user wants to move to a new chat or conversation, hits usage limits, says replies got slow or Claude forgets earlier details, or the conversation has grown long.
token-check
Estimate how many tokens a pasted text, an attached file or the conversation so far takes, what it means for the context window and usage limits, and how to cut it. Use when the user asks how big something is in tokens, why they keep hitting limits, or whether a file is too large to send.
project-context
Turn background the user keeps re-explaining or re-pasting into reusable instructions, so new chats start with it for free. Use when the user repeats the same context, rules, style guide, persona or reference text across messages or chats, says they are tired of explaining the same thing, or asks how to set up a…
brain-log
Show brain sync and evolution history.
writing-handoff
Use when an auto-compaction system reminder appears, when the user explicitly invokes /handoff or asks to "write a handoff" / "save state", or when the user signals they're near the context limit specifically ("running low on context", "almost out of context", "context is getting full"). Do NOT fire on general…