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 commands/vstorm-co/memv/update-plangit clone --depth 1 https://github.com/vstorm-co/memvWhat 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.00011 | $0.00444 |
| Opus 5 | $0.00005 | $0.00222 |
| Sonnet 5 | $0.00002 | $0.00089 |
| Haiku 4.5 | $0.00001 | $0.00044 |
Grade A, and why
update-plan 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.
What it actually says
Update notes/PLAN.md and append to notes/PROGRESS.md based on the current state of the repository and this conversation.
Process
- Run
~/.claude/scripts/plan-status.shto get structured plan status and git state - Read
notes/PLAN.md(previous version — update it, never rewrite from scratch) - Review the conversation for decisions, priorities, and tasks discussed
- Optionally scan recent session logs in
notes/claude/worklog/for additional context - Update
notes/PLAN.md:- Flip
[ ]→[x]for items completed (verified in codebase, not just discussed) - Add new
[ ]items if new work was identified - Remove items that are no longer relevant
- Update the "Last updated" timestamp
- Flip
- Append to
notes/PROGRESS.md(create if missing):- Add a dated entry summarizing what changed in the plan and why
- This file is append-only — never rewrite or remove previous entries
Rules
- Project-scoped only — only include work that changes this project's code, tests, docs, or architecture. Exclude personal tooling, editor config, etc.
- Preserve structure — don't reorganize sections or rewrite prose unless explicitly asked. Only touch checkboxes and add/remove items.
- Verify before checking off — mark items
[x]only if the work is actually in the codebase (committed or staged), not just discussed. - Ground updates in actual repo state (commits, diffs), not just conversation
PROGRESS.md format
## YYYY-MM-DD
- Checked off: <item> — <brief evidence>
- Added: <new item> — <why>
- Removed: <item> — <why>
- Decision: <what was decided and why>
Keep entries concise. One line per change.
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 · 43 lines · 11 tokens per session scan A c472fdd9c132
update-plan is a command published in the GitHub repository vstorm-co/memv (89 stars, last pushed 1mo ago), licensed MIT. It adds 11 tokens to every session and 444 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 commands, from other repositories
build-presentation
Build a design presentation end to end — audience framing, narrative structure, and supporting rationale.
review-pr
Review a pull request (GitHub) or merge request (GitLab) and provide detailed feedback.
create-pr
Create a pull request (GitHub) or merge request (GitLab) from the current branch.
work-on-task
Work on a specific task assigned to you in the agent swarm.
prepare-this-repo
Prepare the current repository to abcd's working conventions — audit it against the abcd record, then adopt the three-tier .abcd/ layout, an AGENTS.md conventions section, and the commit gates. Interim bridge until abcd manages repos directly. Use when the user asks to prepare, onboard, scaffold, or bootstrap a repo…
intent
Press-release intent lifecycle — status, quoted-text create, the implement-readiness gate, and the human planning interview that turns a draft into a planned, specced intent.