Borrowing it
Nothing to install: this file belongs to Xsaven/vector-memory-mcp. 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/Xsaven/vector-memory-mcp/master/.claude/commands/do.mdgit clone --depth 1 https://github.com/Xsaven/vector-memory-mcpWrote 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/xsaven/vector-memory-mcp/do)<a href="https://agentmods.dev/commands/xsaven/vector-memory-mcp/do"><img src="https://agentmods.dev/badge/commands/xsaven/vector-memory-mcp/do/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/xsaven/vector-memory-mcp/do"><img src="https://agentmods.dev/badge/commands/xsaven/vector-memory-mcp/do.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.00021 | $0.04676 |
| Opus 5.5 | $0.00008 | $0.01870 |
| Sonnet 5.5 | $0.00004 | $0.00935 |
| Haiku 4.5 | $0.00002 | $0.00468 |
Grade A, and why
do 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.
How it starts
The opening of the file, as written. The whole thing — 329 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Iron Rules
Zero-distractions (CRITICAL)
ZERO distractions - implement ONLY specified task from $ARGUMENTS. NO creative additions, NO unapproved features, NO scope creep.
- why: Ensures focused execution and prevents feature drift
- on_violation: Abort immediately. Return to approved plan.
Approval-gates-mandatory (CRITICAL)
User approval REQUIRED at Requirements Analysis gate and Execution Planning gate. NEVER proceed without explicit confirmation.
- why: Maintains user control and prevents unauthorized execution
- on_violation: STOP. Wait for user approval before continuing.
Atomic-tasks-only (CRITICAL)
Each agent task MUST be small and focused: maximum 1-2 files per agent invocation. NO large multi-file changes.
- why: Prevents complexity, improves reliability, enables precise tracking
- on_violation: Break task into smaller pieces. Re-plan with atomic steps.
No-improvisation (CRITICAL)
Execute ONLY approved plan steps. NO improvisation, NO "while we're here" additions, NO proactive suggestions during execution.
- why: Maintains plan integrity and predictability
- on_violation: Revert to last approved checkpoint. Resume approved steps only.
Execution-mode-flexible (HIGH)
Execute agents sequentially BY DEFAULT. Allow parallel execution when: 1) tasks are independent (no file/context conflicts), 2) user explicitly requests parallel mode, 3) optimization benefits outweigh tracking complexity.
- why: Balances safety with performance optimization
- on_violation: Validate task independence before parallel execution. Fallback to sequential if conflicts detected.
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 · 329 lines · 21 tokens per session scan A 2f8568f57584
do is a command published in the GitHub repository Xsaven/vector-memory-mcp (0 stars, last pushed 8mo ago), licensed MIT. It adds 21 tokens to every session and 4,676 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-09-01.
do compared with commands from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| doXsaven/vector-memory-mcp | Command | 0 | 8mo ago | MIT | A | 21 | Claude Code |
| checklistgithub/spec-kit | Command | 148k | yesterday | MIT | A | 13 | Claude Code |
| clarifygithub/spec-kit | Command | 148k | yesterday | MIT | A | 27 | Claude Code |
| specifygithub/spec-kit | Command | 148k | yesterday | MIT | A | 13 | Claude Code |
| analyzegithub/spec-kit | Command | 148k | yesterday | MIT | A | 26 | Claude Code |
| convergegithub/spec-kit | Command | 148k | yesterday | MIT | A | 35 | Claude Code |
| implementgithub/spec-kit | Command | 148k | yesterday | MIT | A | 14 | Claude Code |