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-createnpx skills add alivecontext/alive --skill alive-creategit clone --depth 1 https://github.com/alivecontext/aliveWhat 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.00019 | $0.00588 |
| Opus 5 | $0.00010 | $0.00294 |
| Sonnet 5 | $0.00004 | $0.00118 |
| Haiku 4.5 | $0.00002 | $0.00059 |
Grade A, and why
alive-create 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 2d 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
Create Walnut
Something new is emerging. It needs its own walnut.
Ask
What kind of walnut?
1. Venture (04_Ventures/) -- revenue intent
2. Experiment (05_Experiments/) -- testing grounds
3. Person (02_Life/people/) -- someone entering the orbit
4. Life area (02_Life/) -- personal goal or domain
5. Project (nested under existing walnut)
Then ask:
- Name: kebab-case (e.g.,
nova-station) - Goal: one sentence
- Rhythm: daily / weekly / biweekly / monthly
Scaffold
Create via terminal:
WALNUT_PATH="$ALIVE_WORLD_ROOT/[domain]/[name]"
mkdir -p "$WALNUT_PATH/_kernel"
Write three kernel files:
key.md
---
type: [venture/experiment/person/life/project]
goal: [one sentence]
created: [today]
rhythm: [rhythm]
people: []
tags: []
links: []
---
[Brief description of what this walnut is about.]
log.md
---
walnut: [name]
created: [today]
last-entry: [today]
entry-count: 1
summary: Walnut created.
---
## [today] -- squirrel:[session_id]
**Type:** creation
Walnut created. [Goal]. [Any initial context from conversation.]
signed: squirrel:[session_id]
insights.md
---
walnut: [name]
updated: [today]
squirrel: [session_id]
sections: []
---
tasks.json + completed.json
echo '{"tasks": []}' > "$WALNUT_PATH/_kernel/tasks.json"
echo '{"completed": []}' > "$WALNUT_PATH/_kernel/completed.json"
Run projection
python3 "$ALIVE_WORLD_ROOT/.alive/scripts/project.py" --walnut "[relative_path]"
After Creation
- If this walnut is a sub-walnut, add
parent: [[parent]]to key.md - Add
[[name]]to parent's key.md links - Offer to create the first bundle
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.
- 2d ago First seen · 112 lines · 19 tokens per session scan A 94db7cde7864
alive-create is a skill published in the GitHub repository alivecontext/alive (127 stars, last pushed 7d ago), licensed MIT. It adds 19 tokens to every session and 588 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
cco-task
Organize work by task and track tokens/cost per task — start a task, list tasks, or mark the active one done. Pairs with /cco-pack to load minimal context per task.
backlog-technical-project-manager
Technical project management for Backlog.md workstreams using coordinated sub-agents. Use only when the user explicitly asks Codex to take over one or more existing Backlog.md tasks (for example: "act as TPM", "coordinate these tasks", "delegate to sub-agents"). Orchestrate planning, implementation, and finalization…
omh-agent-board
This is a Hermes-native agent-board workflow skill.
omh-idea-to-deploy
This is a Hermes-native idea-to-deploy workflow skill.
triage-sweep
Backfill labels across oh-my-hermes issues and pull requests. Run manually to sweep everything currently unlabeled, or pass a number to triage one item. Use when issues and PRs have accumulated without labels, after adding a new label to .github/labels.yml, or before a release when the backlog needs to be readable by…
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.