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-context-rebuildnpx skills add alivecontext/alive --skill session-context-rebuildgit 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-context-rebuild)<a href="https://agentmods.dev/skills/alivecontext/alive/session-context-rebuild"><img src="https://agentmods.dev/badge/skills/alivecontext/alive/session-context-rebuild.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.00072 | $0.01636 |
| Opus 5 | $0.00036 | $0.00818 |
| Sonnet 5 | $0.00014 | $0.00327 |
| Haiku 4.5 | $0.00007 | $0.00164 |
Grade A, and why
alive:session-context-rebuild 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 5d 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 — 154 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Session Context Rebuild
You're returning to work that spans multiple sessions — possibly conflicting ones. The context window is empty but the walnut isn't. This skill dispatches subagents to deeply reconstruct what happened, what changed, where conflicts exist, and what the merged state should be. Then you resume with full context as if you never left.
When to Use
- Returning to a walnut after days/weeks away
- Context was lost to compaction mid-session
- Multiple sessions touched the same walnut in parallel and need merging
- Picking up someone else's work in a shared walnut
- "What was I doing here?" moments
Process
Phase 1: Scout (single agent)
Dispatch one general-purpose subagent to map the territory. It reads the session-history/SKILL.md file and applies its browse logic against .alive/_squirrels/, then reports back:
- Which sessions touched this walnut, when, by whom (engine)
- Which files each session worked on (
working:field in squirrel YAML) - Which bundles were active
- Whether sessions overlap (parallel/conflicting work)
- Unsaved stash items from crashed sessions
Cross-walnut detection: the scout performs two queries, not one:
- Walnut-tagged match — squirrel YAMLs where
walnut: {target}(the obvious set) - Routed-stash match — squirrel YAMLs where any stash item's
routed:field contains the target walnut name (catches maintenance sessions withwalnut: nullthat routed work to this walnut)
Merge-deduplicate by session_id. Report both counts so the user sees "5 walnut-tagged + 1 cross-walnut routed" instead of just "5 sessions."
╭─ 🐿️ context rebuild — scouting
│ Found 5 sessions on this walnut (last 2 weeks)
│ 3 sequential, 2 overlapping (possible conflicts)
│ 12 files touched, 2 bundles active
│
│ ▸ Rebuild scope?
│ 1. All 5 sessions (full rebuild)
│ 2. Last 3 only
│ 3. Just the 2 conflicting sessions
╰─
Phase 2: Deep Read (agent swarm)
Based on scope, dispatch parallel subagents — one per session or one per domain:
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.
- 5d ago First seen · 154 lines · 72 tokens per session scan A 9df1f94275fb
alive:session-context-rebuild is a skill published in the GitHub repository alivecontext/alive (127 stars, last pushed 9d ago), licensed MIT. It adds 72 tokens to every session and 1,636 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-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.
cco-pack
Build an optimal context pack for the user's task — ranked file list with offset/limit suggestions, based on git state, mentioned paths, and historical patterns.
cco
Context Control Center — one screen for budget, $ spent, tokens saved, waste, last prompt grade, the active task, and ready-to-run optimization actions.
cco-doctor
Health check for the context-optimizer plugin install — verifies versions, hooks, data dir, model config, and reports any issues.
cco-templates
Manage context templates for common task types.
cco-replay
Show recent session summaries for quick context recovery.