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/my-context-graphnpx skills add alivecontext/alive --skill my-context-graphgit clone --depth 1 https://github.com/alivecontext/aliveWrote this? Show the measurements
A badge for your README with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them.
[](https://agentmods.dev/skills/alivecontext/alive/my-context-graph)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.00050 | $0.01918 |
| Opus 5 | $0.00025 | $0.00959 |
| Sonnet 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 3d 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.
- 3d 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 (127 stars, last pushed 8d ago), licensed MIT. It adds 50 tokens to every session and 1,918 once invoked, about $0.0003 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
crit-cli
Use when an agent needs to author or reply to crit inline comments programmatically (including multi-agent workflows commenting on shared code/plans/docs/proposals), publish or unpublish a crit review with crit share, sync a crit review to or from a GitHub PR or GitLab MR, or read/interpret a crit review JSON file.…
crit
Review code changes, a plan, a live page (running dev server), or a local HTML file with Crit inline comments and structured human feedback. Use only when the user explicitly invokes /crit or directly asks to use Crit; a generic review request does not count.
crit-story
Author a crit story 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.
cco-config
View and tune CCO's behavior thresholds — re-read warnings, cache staleness, prompt-coach length bands, and the /cco-pack budget cap.
cco-budget
Configure token budget limits, auto-compact settings, and view current budget status (model-aware — Opus 4.8 default, full 1M context at standard price).
cco-overhead
Audit the fixed context overhead every session starts with — system prompt, MCP tools, agents, CLAUDE.md, memory — measured from real transcript usage.