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-dailygit 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-daily)<a href="https://agentmods.dev/skills/alivecontext/alive/alive-daily"><img src="https://agentmods.dev/badge/skills/alivecontext/alive/alive-daily/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-daily"><img src="https://agentmods.dev/badge/skills/alivecontext/alive/alive-daily.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.00548 |
| Opus 5.5 | $0.00008 | $0.00219 |
| Sonnet 5.5 | $0.00004 | $0.00110 |
| Haiku 4.5 | $0.00002 | $0.00055 |
Grade A, and why
alive-daily 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
Daily
The morning operating system. Sync all inputs, read everything, surface what matters.
1. Sync Inputs
Run available sync scripts (if configured):
# Check which sync scripts exist
ls "$ALIVE_WORLD_ROOT/.alive/scripts/"*-sync.* 2>/dev/null
Common syncs: Gmail, Slack, Fathom (meeting transcripts). Each writes to 03_Inbox/.
2. Check Inbox
find "$ALIVE_WORLD_ROOT/03_Inbox" -type f -not -name ".*" 2>/dev/null | wc -l
If files exist, list them with routing suggestions.
3. Read All Active Walnuts
For each non-archive walnut, read _kernel/now.json. Extract:
- Phase, blockers, urgent + active task lists, health signal
4. Check Unrouted Stash
cat "$ALIVE_WORLD_ROOT/.alive/stash.json" 2>/dev/null
Present any pending items grouped by destination walnut.
5. Check Unsaved Sessions
Scan .alive/_squirrels/ for entries with saves: 0. These sessions may have lost work.
6. Surface the Day
Morning -- [date]
Priority:
1. [walnut] -- [top urgent task]
2. [walnut] -- [top urgent task]
Active (on rhythm):
[walnut] [phase] [top urgent or active task]
[walnut] [phase] [top urgent or active task]
Needs Attention:
[walnut] waiting [N] days past rhythm
[walnut] quiet [blocker]
People:
[[person]] last contact [N] days ago
Inbox: [N] unrouted files
Stash: [N] pending items
What to work on?
7. Route
User picks a walnut -> invoke /alive-load for that walnut.
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 · 90 lines · 20 tokens per session scan A 7d507edf03ec
alive-daily is a skill published in the GitHub repository alivecontext/alive (130 stars, last pushed 19d ago), licensed MIT. It adds 20 tokens to every session and 548 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.
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.