Borrowing it
Nothing to install: this file belongs to vstorm-co/memv. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/vstorm-co/memv/main/.claude/commands/update-plan.mdgit clone --depth 1 https://github.com/vstorm-co/memvWrote 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/vstorm-co/memv/update-plan)<a href="https://agentmods.dev/commands/vstorm-co/memv/update-plan"><img src="https://agentmods.dev/badge/commands/vstorm-co/memv/update-plan/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/vstorm-co/memv/update-plan"><img src="https://agentmods.dev/badge/commands/vstorm-co/memv/update-plan.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.00011 | $0.00444 |
| Opus 5.5 | $0.00004 | $0.00178 |
| Sonnet 5.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 2mo 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.
- 2mo 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 (91 stars, last pushed 1mo ago), licensed MIT. It adds 11 tokens to every session and 444 once invoked, about $0.0000 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 commands, from other repositories
setup-workflow
Set up a team's operating rhythm end to end — rituals, task flow, tooling, review gates, and version control.
plan-sprint
Run a design sprint end to end — challenge framing, schedule, exercises, and prototype test plan.
dashboard-proposal-detach
Detach the OpenSpec change from a session. Usage /dashboard:proposal-detach.
dashboard-session-fork
Fork a session into a new one. Usage /dashboard:session-fork.
dashboard-session-hide
Hide a session from the dashboard list. Usage /dashboard:session-hide.
multi-repo-swarm
Coordinate AI swarms across multiple repositories, enabling organization-wide automation and intelligent cross-project collaboration.