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-bundlegit 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-bundle)<a href="https://agentmods.dev/skills/alivecontext/alive/alive-bundle"><img src="https://agentmods.dev/badge/skills/alivecontext/alive/alive-bundle/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-bundle"><img src="https://agentmods.dev/badge/skills/alivecontext/alive/alive-bundle.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.00555 |
| Opus 5.5 | $0.00008 | $0.00222 |
| Sonnet 5.5 | $0.00004 | $0.00111 |
| Haiku 4.5 | $0.00002 | $0.00056 |
Grade A, and why
alive-bundle 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
Bundle Management
Bundles are self-contained units of work inside a walnut. Any folder with a context.manifest.yaml is a bundle.
Create
What's this bundle for?
1. Outcome -- produces something specific (deliverable, has a done state)
2. Evergreen -- accumulates context over time (collection, ongoing)
Ask for:
- Name: kebab-case (e.g.,
website-rebuild) - Goal: one sentence describing the deliverable or collection
Scaffold:
BUNDLE_PATH="$WALNUT_PATH/[bundle-name]"
mkdir -p "$BUNDLE_PATH/raw"
Write context.manifest.yaml:
goal: "[goal]"
status: draft
version: v0.1
sensitivity: private
pii: false
created: [today]
updated: [today]
context: |
Bundle created. [Initial context from conversation.]
sources: []
linked_bundles: []
tags: []
squirrels: [[session_id]]
active_sessions:
- session: [session_id]
engine: hermes-agent
started: [now]
working_on: "Initial setup"
Write tasks.json:
{"tasks": []}
Status Lifecycle
draft -> prototype -> published -> done
- draft -- actively worked on, markdown only
- prototype -- has a visual (HTML), maybe shared with 1-2 people
- published -- shared externally
- done -- outputs complete, bundle stays as historical record
Graduate
When a *-v1.md or *-v1.html file exists:
v1 exists. Graduate this bundle?
1. Yes, mark as done
2. Yes, mark as published
3. Not yet
Flip status: in manifest. Bundle folder stays where it is.
Routing
When content arrives:
- Same goal -> same bundle
- Related but different goal -> new bundle, link to existing
- Ambiguous -> ask once
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 · 106 lines · 20 tokens per session scan A f835d356e5db
alive-bundle is a skill published in the GitHub repository alivecontext/alive (130 stars, last pushed 18d ago), licensed MIT. It adds 20 tokens to every session and 555 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
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…
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…
session-close
Use at a session boundary — the session looks done, or you are breaking mid-work. Routes by fulfillment: goal delivered whole → done-close (closeout moves + this session's carry file cleared); in-motion remainder → park-close (card-anchored remainder appended as a ## Progress block on the owning card, only what no…
project-sync
On-demand AI-powered sync of a project's repo state into the brain vault. Reads live git/GitHub/Jira data, updates the project status doc, and makes targeted edits to relevant brain docs where content is clearly stale. Triggered by "/project-sync [name]", "sync [project]", "what's the current state of [project]".