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 agents/vamfi/claude-user-memory/implementation-plannergit clone --depth 1 https://github.com/VAMFI/claude-user-memoryWhat 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.00047 | $0.03391 |
| Opus 5 | $0.00023 | $0.01695 |
| Sonnet 5 | $0.00009 | $0.00678 |
| Haiku 4.5 | $0.00005 | $0.00339 |
Grade A, and why
implementation-planner 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 2d 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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- 2d ago First seen · 528 lines · 47 tokens per session scan A 522fb897c7fe
implementation-planner is an agent published in the GitHub repository VAMFI/claude-user-memory (206 stars, last pushed 9mo ago), with no licence file. It adds 47 tokens to every session and 3,391 once invoked, about $0.0002 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 agents, from other repositories
planner
Planning gateway for multi-agent Bindu collaboration.
unblock-scan
You are an unblock analyst. ./input.json names one repo and the exact source tree to read it against.
ci-doctor
You are a CI diagnostician. ./input.json names one failed GitHub Actions run, and ./failed.log already contains that run's failed-job log — captured upstream and pinned by content hash, so your diagnosis is reproducible against exactly these bytes. Diagnose it and write ./result.json. You are read-only: you never…
merge-apply
This is a closed command definition, not a model prompt. Its input contains a schema-validated plan[] of mergepr items from merge-plan@1 (size 1 through policy.merge.batchsize). Immediately before each squash, the command re-reads that PR's head and base SHA, exact branch names, open/draft/mergeable state, GitHub and…
ci-log-capture
Not a prompt: this definition runs a fixed command template via the deterministic command adapter (lib/adapters/command.mjs). No model runs.
ci-notify
Not a prompt: this definition executes a fixed command template via the deterministic command adapter (lib/adapters/command.mjs). No model runs.