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 my-context-graphgit 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/my-context-graph)<a href="https://agentmods.dev/skills/alivecontext/alive/my-context-graph"><img src="https://agentmods.dev/badge/skills/alivecontext/alive/my-context-graph/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/my-context-graph"><img src="https://agentmods.dev/badge/skills/alivecontext/alive/my-context-graph.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.00050 | $0.01918 |
| Opus 5.5 | $0.00020 | $0.00767 |
| Sonnet 5.5 | $0.00010 | $0.00384 |
| Haiku 4.5 | $0.00005 | $0.00192 |
Grade A, and why
alive:my-context-graph 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 — 218 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Map
Visual overview of the entire ALIVE world — connections, clusters, health.
Not a list (that's the tree in alive:world). Not a search (that's alive:search-world). Map is spatial — it shows how everything connects and where the energy is.
What It Does
1. Generate the World Index
Run generate-index.py from the plugin to walk all walnuts and collect frontmatter. Always use the plugin cache copy — never copy scripts to the world (world-local copies drift from the plugin and produce stale data).
python3 "$ALIVE_PLUGIN_ROOT/scripts/generate-index.py" "$WORLD_ROOT"
The script walks all directories for key.md files, handling both _kernel/key.md (current structure) and root-level key.md (flat/legacy structure). It deduplicates entries and skips template walnuts.
Collected data per walnut:
- Name, type, goal, phase, rhythm, tags
- People (from
key.mdpeople:field — multi-line list) - Links (from
key.mdlinks:field — wikilink extraction) - Parent (from
key.mdparent:field) - Bundles (detected by
*/context.manifest.yamlin walnut root — name, status, goal) - Task counts (from
_kernel/now.jsonif present) - Last updated (from
_kernel/now.jsonupdatedfield)
Projection tiers: The graph supports three projection levels for controlling visual density:
- Tier 1 — Walnuts only — just the walnut nodes and their connections. Fast, clean overview.
- Tier 2 — Walnuts + People — adds people nodes that bridge multiple walnuts. Shows relationship topology.
- Tier 3 — Full graph — walnuts, people, bundles, tags. Maximum detail. Can get dense in large worlds.
Default to Tier 2. Offer toggle controls for Tier 1 (simplified) and Tier 3 (full detail).
Outputs:
.alive/_index.yaml— human-readable world index.alive/_index.json— machine-readable for graph consumption
2. Render the Graph
Run generate-graph.py from the plugin to read the JSON index and generate an interactive D3.js graph.
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 · 218 lines · 50 tokens per session scan A 0ae05cd8e7ea
alive:my-context-graph is a skill published in the GitHub repository alivecontext/alive (130 stars, last pushed 17d ago), licensed MIT. It adds 50 tokens to every session and 1,918 once invoked, about $0.0002 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…