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/alive-loadnpx skills add alivecontext/alive --skill alive-loadgit 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-load)<a href="https://agentmods.dev/skills/alivecontext/alive/alive-load"><img src="https://agentmods.dev/badge/skills/alivecontext/alive/alive-load.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.00026 | $0.00567 |
| Opus 5 | $0.00013 | $0.00283 |
| Sonnet 5 | $0.00005 | $0.00113 |
| Haiku 4.5 | $0.00003 | $0.00057 |
Grade A, and why
alive-load 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.
What it actually says
Load Walnut
Load a walnut's context. Read the brief pack, resolve people, surface one observation, ask what to work on.
If No Walnut Named
List available walnuts grouped by domain. Use terminal to run:
find "$ALIVE_WORLD_ROOT" -name "key.md" -path "*/_kernel/*" | grep -v "01_Archive" | sort
Show as a numbered list. Let the user pick.
Brief Pack (3 files)
Read these three files for the named walnut. Nothing else at this stage.
_kernel/key.md-- full (identity, people, links, rhythm)_kernel/now.json-- full (phase, bundles, tasks, sessions, blockers)_kernel/insights.md-- first 20 lines only (frontmatter, section names)
Show what you read:
> key.md [walnut name] -- [type], [rhythm], [N] people
> now.json Phase: [phase]. Urgent: [N] / Active: [N]. Bundles: [N] active.
> insights.md [N] domain knowledge sections
Spotted
One observation grounded in what you just read. A stale blocker, an urgent task that has been sitting, a bundle with no recent sessions. If nothing genuine, skip it.
Then Ask
[walnut name]
Goal: [from key.md]
Phase: [from now.json]
Bundle: [active bundle name] ([status])
What are you working on?
1. Continue active bundle
2. Start new
3. Go deeper (log, linked walnuts)
4. Just chat
If no active bundle exists, drop option 1 and renumber so the menu is 1. Start new 2. Go deeper 3. Just chat.
During Work
- Stash decisions, tasks, notes in conversation
- Watch for people updates, bundle fits, capturable content
- When another walnut is mentioned, ask before loading it
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 · 77 lines · 26 tokens per session scan A 3bbaa2f273b8
alive-load is a skill published in the GitHub repository alivecontext/alive (127 stars, last pushed 8d ago), licensed MIT. It adds 26 tokens to every session and 567 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
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.