What is alive-bundle?

A manager for bundles, which are self-contained work folders inside a walnut. It creates their context file and task list and tracks stages such as draft, prototype, published, and done.

Use it to start a deliverable or ongoing collection, maintain its context and tasks, link related work, and graduate it through its lifecycle.

It gives each focused piece of work its own goal, context, tasks, sources, and progress status.

alive-bundle — Skill by alivecontext

Install

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.

agentmods

npx agentmods add skills/alivecontext/alive/alive-bundle

Any agent

npx skills add alivecontext/alive --skill alive-bundle

Clone the repo

git clone --depth 1 https://github.com/alivecontext/alive

Made for: Claude Code, Codex.

Per session 20 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 555 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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.00020	$0.00555
Opus 5	$0.00010	$0.00278
Sonnet 5	$0.00004	$0.00111
Haiku 4.5	$0.00002	$0.00056

Measured 3d ago against content hash f835d356e5db, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 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.

hermes/hermes-skills/alive-bundle/SKILL.md · 106 lines

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

Changes

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 · 106 lines · 20 tokens per session scan A f835d356e5db

Subscribe to this mod's changes

alive-bundle is a skill published in the GitHub repository alivecontext/alive (127 stars, last pushed 8d ago), licensed MIT. It adds 20 tokens to every session and 555 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.

Memory and context Project management ai-tools claude-code claude-code-plugin cli context-management markdown

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.…

tomasz-tomczyk/crit · 110 tokens

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.

tomasz-tomczyk/crit · 55 tokens

alive-bundle