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 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/world)<a href="https://agentmods.dev/skills/alivecontext/alive/world"><img src="https://agentmods.dev/badge/skills/alivecontext/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/world"><img src="https://agentmods.dev/badge/skills/alivecontext/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.00063 | $0.03266 |
| Opus 5.5 | $0.00025 | $0.01306 |
| Sonnet 5.5 | $0.00013 | $0.00653 |
| Haiku 4.5 | $0.00006 | $0.00327 |
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.
How it starts
The opening of the file, as written. The whole thing — 273 lines — stays where its author put it; the contents beside it link to each section on GitHub.
World
This is Mission Control. When the human opens their world, it should feel like booting an operating system — everything they care about, at a glance, with clear paths to action.
NOT a database dump. NOT a flat list. A living view of their world, grouped by what matters, showing relationships, surfacing what needs attention.
Load Sequence
- Read
.alive/_index.yaml— one read, everything the dashboard needs: every walnut's type, goal, phase, rhythm, updated, people, links, tags, bundles, and parent relationships. The SessionStart hook injects<WORLD_INDEX_BRIEF>(names, paths, phases, people) which is enough to orient, but the dashboard's goal lines, rhythm warnings and bundle counts come from the full index file. Older plugin versions injected the full index as<WORLD_INDEX>; if that's in context, use it and skip the read. - If no index exists at all — generate it first (
python3 "$ALIVE_PLUGIN_ROOT/scripts/generate-index.py" "$WORLD_ROOT"), then read the output. Fall back to manual scanning only on first-time setup before the index infrastructure exists. - Freshness check — read the
generated:timestamp from the index. Display it in the dashboard header. If older than 10 minutes, show a warning. If older than 1 hour, suggest regeneration. This makes index staleness visible instead of invisible. - Build the tree from the index — parent/child relationships from
parent:field - Lightweight fresh checks — one Bash call each, no subagents, no Explore agents:
- Unsaved sessions with stash: already in the index as
unsaved_with_stash:. If non-zero, surface in the Attention section. No bash loop needed. - Unrouted inputs: resolve the world root via the doctor JSON surface, then list the absolute path. Never use a relative
ls 03_Inbox/— it silently fails when the Bash tool's cwd isn't the world root. One-liner:
Doctor's pinned-strategy result is the authoritative resolver — preferred over raw config-file reads, which mangle paths with internal whitespace. Just the filenames, no deep reads.WR=$(alive doctor --check=world-root --json | jq -r '.world_root') && [ -n "$WR" ] && ls "$WR/03_Inbox/" 2>/dev/null | grep -v '^\.' | grep -v '^Icon' - API context: only if context sources are listed in the session start injection (already in your context from the hook — do NOT re-read preferences.yaml).
- Unsaved sessions with stash: already in the index as
- Compute attention items from fresh checks + index staleness signals
- Inbox triage (background) — if
03_Inbox/has items, dispatch a background agent to triage them. Don't wait for it — render the dashboard immediately, the triage results arrive while the human reads.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 Changed 23fdeee1a187
- 1mo ago First seen · 273 lines · 63 tokens per session scan A 604d7a905a3d
alive:world is a skill published in the GitHub repository alivecontext/alive (130 stars, last pushed 15d ago), licensed MIT. It adds 63 tokens to every session and 3,266 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
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.
resuming-from-handoff
Use when user invokes /handoff-resume, says "pick up where we left off", "continue from last session", "what was I working on", or starts a session with a reference to prior work that may be captured in a previous handoff 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.
slackcli
Read, send, search, and manage Slack workspaces with the slackcli binary. Installs slackcli if missing and checks or proposes authentication first. Use whenever the user mentions Slack or pastes a slack.com link.