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.
git clone --depth 1 https://github.com/Fredje777/claude-zenvibeWrote 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/commands/fredje777/claude-zenvibe/zenresume)<a href="https://agentmods.dev/commands/fredje777/claude-zenvibe/zenresume"><img src="https://agentmods.dev/badge/commands/fredje777/claude-zenvibe/zenresume/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/commands/fredje777/claude-zenvibe/zenresume"><img src="https://agentmods.dev/badge/commands/fredje777/claude-zenvibe/zenresume.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00056 | $0.00727 |
| Opus 5 | $0.00028 | $0.00364 |
| Sonnet 5 | $0.00011 | $0.00145 |
| Haiku 4.5 | $0.00006 | $0.00073 |
Grade A, and why
zenresume 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 11d 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 — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The user is resuming after a pause or a conversation compaction. Re-establish context properly before doing anything else.
Output language: Default to English. If CLAUDE.md is in French OR the journal contains French entries, write your briefing in French. Otherwise English.
Workflow
1. Read the journal in full
- Try
docs/JOURNAL.md. If absent, tryJOURNAL.mdat the repo root. - If neither exists, say: "No JOURNAL found. Want to start one, or would you rather brief me verbally?" — then stop and wait.
- Read the journal entirely. The latest entry matters most, but earlier ones carry deferred decisions, refactors, and context still in play.
2. Read project conventions
Read CLAUDE.md at the project root if present. Note the conventions on commits, naming, security, validations, testing — they guide everything you do this session. If multiple CLAUDE.md exist in subdirectories, read the one closest to the work area mentioned in the journal.
3. Check the actual git state
Run, in parallel:
git statusgit log -5 --onelinegit branch --show-current
Compare with the "Git" section of the latest journal entry. If they diverge (new commits, unexpected uncommitted changes, different branch), flag it in your summary.
4. Produce a compact briefing
Output exactly this structure, filled from what you read:
Resumed from docs/JOURNAL.md (entry of <date time>)
You were on: <current task>
Since the pause: <commits visible since pause, or "nothing">
Remaining on this task: <unfinished points>
Proposed next action: <one concrete, actionable sentence>
Attention points noted at pause:
- ...
Active conventions (CLAUDE.md): <2–3 bullets if relevant to the next action>
Shall I resume? (yes / no / different direction)
Keep it under 25 lines. The user wants context, not a re-narration of the journal.
5. Wait for an explicit go-ahead
Do not edit files, run mutating commands, or start the proposed action until the user explicitly confirms ("yes", "go", "ok", "oui", "vas-y" — any clear assent).
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.
- 11d ago First seen · 70 lines · 56 tokens per session scan A 5a11bbbea01a
zenresume is a command published in the GitHub repository Fredje777/claude-zenvibe (2 stars, last pushed 18d ago), licensed MIT. It adds 56 tokens to every session and 727 once invoked, about $0.0003 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-31.
Other commands, from other repositories
setup-context
Set up your Skill Memory — a pm-context.md every skill reads so outputs come back tailored to you.
brain
Set up or use your Professional Brain — init, ingest, recall, or review.
pull-learnings
Pulls shared organization patterns into local org-patterns.toon.
context-stats
Display context window usage and token statistics.
meetings-list
List recent meetings and voice memos. Use when the user asks "what meetings did I have", "show my recent recordings", "any meetings today", "list my voice memos", or wants an overview of their meeting history. Also use when they need to find a specific meeting by browsing rather than searching.
meetings-search
Search meeting transcripts and voice memos for people, topics, decisions, commitments, or remembered ideas. Use when the user asks what was discussed, decided, or said across their meeting history. Not for preparing an upcoming meeting; use $meetings-prep.