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 mine-for-contextgit 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/mine-for-context)<a href="https://agentmods.dev/skills/alivecontext/alive/mine-for-context"><img src="https://agentmods.dev/badge/skills/alivecontext/alive/mine-for-context/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/mine-for-context"><img src="https://agentmods.dev/badge/skills/alivecontext/alive/mine-for-context.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.00063 | $0.02253 |
| Opus 5.5 | $0.00025 | $0.00901 |
| Sonnet 5.5 | $0.00013 | $0.00451 |
| Haiku 4.5 | $0.00006 | $0.00225 |
Grade A, and why
alive:mine-for-context 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 — 226 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mine
Deep extraction. Turn raw sources into structured context.
Not a quick search (that's find). Not session timeline (that's history). Mine is the heavy operation — reading source material systematically, extracting everything of value, and routing it into the world.
When It Fires
- The human says "mine this", "extract from these", "what's buried in here"
alive:session-historyescalates — "these sessions look rich, want to deep-mine them?"- The human points at a folder of transcripts, documents, or exports
- A bundle has raw sources that haven't been fully processed
- The human asks "what have I missed?" or "find everything about X in my sources"
What It Does
0. Pre-check: Source Location
Before mining, check whether the source file lives inside a bundle's raw/ folder:
- In a bundle — proceed normally. Phase 4 tracking writes to that bundle's
context.manifest.yamldiscovered:field. - Loose file (inbox, walnut root, or anywhere without a manifest) — enter loose-mine mode. Mining still works, but tracking state writes to
$WORLD_ROOT/.alive/_mining-log.jsoninstead of a bundle manifest. This prevents duplicate work if the same file is mined again before being captured into a bundle.
// .alive/_mining-log.json — created on first loose mine
{
"mined": [
{
"path": "03_Inbox/Will x Ben Standup.md",
"mined_at": "2026-04-16T10:30:00Z",
"items_extracted": 14,
"routed_to": "alive-os"
}
]
}
If the file appears in _mining-log.json already, warn: "This file was mined on {date} ({N} items extracted). Mine again or skip?"
1. Assess Source Material
Scan what's available. Don't read everything — just understand the landscape.
╭─ squirrel scanning sources
│
│ client-calls/raw/ — 12 transcripts (3 unprocessed)
│ research/raw/ — 8 documents (5 unprocessed)
│ .alive/_squirrels/ — 23 sessions (8 with rich stash, 4 unmined transcripts)
│
│ Total: 43 sources, 12 unprocessed, 4 unmined sessions
╰─
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 · 226 lines · 63 tokens per session scan A d4b0d7852309
alive:mine-for-context is a skill published in the GitHub repository alivecontext/alive (130 stars, last pushed 17d ago), licensed MIT. It adds 63 tokens to every session and 2,253 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…