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 alive-worldgit 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-world)<a href="https://agentmods.dev/skills/alivecontext/alive/alive-world"><img src="https://agentmods.dev/badge/skills/alivecontext/alive/alive-world/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/alive-world"><img src="https://agentmods.dev/badge/skills/alivecontext/alive/alive-world.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.00020 | $0.00478 |
| Opus 5.5 | $0.00008 | $0.00191 |
| Sonnet 5.5 | $0.00004 | $0.00096 |
| Haiku 4.5 | $0.00002 | $0.00048 |
Grade A, and why
alive-world 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.
What it actually says
World View
Show the full world grouped by ALIVE domain.
Gather State
For each walnut, read _kernel/now.json (or fall back to _kernel/key.md frontmatter). Extract:
- name, goal, phase, rhythm, updated date
Calculate health from rhythm + updated:
- active -- within rhythm
- quiet -- 1-2x past rhythm
- waiting -- 2x+ past rhythm
Display
ALIVE World -- [N] walnuts
Life (02_Life/)
[name] [health] [goal excerpt]
[name] [health] [goal excerpt]
Ventures (04_Ventures/)
[name] active [goal excerpt]
[name] quiet [goal excerpt] (12 days)
[name] waiting [goal excerpt] (34 days)
Experiments (05_Experiments/)
[name] [health] [goal excerpt]
Needs Attention:
- [walnut] has been waiting 34 days (rhythm: weekly)
- [walnut] has 3 urgent tasks
- [walnut] has unrouted stash items
What to do?
1. Load a walnut (name or number)
2. Tidy (clean up stale walnuts)
3. Find (search across world)
4. History (recent sessions)
5. Map (context graph)
Skip Archive
Never show 01_Archive walnuts in the dashboard. They're graduated, not active.
Skip Inbox
03_Inbox is a buffer. Show unrouted file count if any exist, but don't list individual files.
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 · 72 lines · 20 tokens per session scan A cb4e3332307f
alive-world is a skill published in the GitHub repository alivecontext/alive (131 stars, last pushed 24d ago), licensed MIT. It adds 20 tokens to every session and 478 once invoked, about $0.0001 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
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 and continue the interactive review loop 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.
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.
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…
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…