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 alive-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/alive-history)<a href="https://agentmods.dev/skills/alivecontext/alive/alive-history"><img src="https://agentmods.dev/badge/skills/alivecontext/alive/alive-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/alive-history"><img src="https://agentmods.dev/badge/skills/alivecontext/alive/alive-history.svg" alt="Reviewed on agentmods" width="80" 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.00025 | $0.00557 |
| Opus 5 | $0.00013 | $0.00279 |
| Sonnet 5 | $0.00005 | $0.00111 |
| Haiku 4.5 | $0.00003 | $0.00056 |
Grade A, and why
alive-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 9d 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
Session History
Search squirrel entries and logs for past session context.
Sources
- Squirrel entries --
.alive/_squirrels/*.yaml(session metadata, stash, recovery state) - Log entries --
_kernel/log.md(decisions, narrative, signed entries) - Stash file --
.alive/stash.json(unrouted items from sessions)
Search
If the user asks about a specific walnut:
# Read that walnut's log
cat "$ALIVE_WORLD_ROOT/[walnut_path]/_kernel/log.md"
# Find squirrel entries for that walnut
grep -l "[walnut_name]" "$ALIVE_WORLD_ROOT/.alive/_squirrels/"*.yaml 2>/dev/null
If the user asks about a topic or person:
# Search all logs
grep -rl "[query]" "$ALIVE_WORLD_ROOT"/*/_kernel/log.md "$ALIVE_WORLD_ROOT"/*/*/_kernel/log.md 2>/dev/null
# Search squirrel entries
grep -rl "[query]" "$ALIVE_WORLD_ROOT/.alive/_squirrels/"*.yaml 2>/dev/null
If the user asks about recent sessions:
# List recent squirrel entries by date
ls -lt "$ALIVE_WORLD_ROOT/.alive/_squirrels/"*.yaml 2>/dev/null | head -10
Display
Recent sessions for [walnut/topic]:
[date] -- squirrel:[id] ([engine])
Walnut: [name]
Bundle: [bundle or none]
Summary: [from log entry or recovery_state]
Stash: [N] items ([routed/unrouted])
[date] -- squirrel:[id] ([engine])
...
Load full log entry?
1. [session id] -- [date]
2. [session id] -- [date]
3. Search for something else
Escalation
If the user needs deeper context extraction from session transcripts, suggest /alive-mine for heavy mining.
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.
- 9d ago First seen · 83 lines · 25 tokens per session scan A 6f554dfaf367
alive-history is a skill published in the GitHub repository alivecontext/alive (127 stars, last pushed 13d ago), licensed MIT. It adds 25 tokens to every session and 557 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 skills, from other repositories
cco-patterns
Share learned file patterns across a team — export an anonymized digest of what's usually waste/useful/co-edited, and import a teammate's so a fresh clone benefits day one.
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…
crit-story
Author a crit story and continue the interactive review loop only when the user explicitly invokes crit-story or directly asks you to generate a crit story. Do not infer this skill from generic review, PR, or diff-review requests.
mnemon
Persistent graph-based memory. Recall context before responding, remember insights after. Each group has private memory; global memory is read-only.
mnemon
Persistent memory CLI for LLM agents. Store facts, recall past knowledge, link related memories, manage lifecycle.