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 instructions/putervision/vision-memory-mcp/claude-mdgit clone --depth 1 https://github.com/putervision/vision-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/instructions/putervision/vision-memory-mcp/claude-md)<a href="https://agentmods.dev/instructions/putervision/vision-memory-mcp/claude-md"><img src="https://agentmods.dev/badge/instructions/putervision/vision-memory-mcp/claude-md.svg" alt="Measured on agentmods" 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 | $0.01791 | $0.01791 |
| Opus 5 | $0.00896 | $0.00896 |
| Sonnet 5 | $0.00358 | $0.00358 |
| Haiku 4.5 | $0.00179 | $0.00179 |
Grade B, and why
vision-memory-mcp CLAUDE.md scanned grade B with 1 finding 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 4d 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
* **Google Antigravity (`~/.gemini/config/config.json`)**: Add these rules to your `"globalPermissionGrants"` -> `"allow"` list: 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.
- 4d ago First seen · 85 lines · 1,791 tokens per session scan B 93d560102d4c
vision-memory-mcp CLAUDE.md is an instructions file published in the GitHub repository putervision/vision-memory-mcp (59 stars, last pushed today), with no licence file. It adds 1,791 tokens to every session, about $0.0090 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
ai-agent-history-rag-mcp CLAUDE.md
Instructions for no13productions/ai-agent-history-rag-mcp, covering claude.md, knowledge source, project overview, tech stack and build and run commands.
ssd-ai memory-bank.instructions.md
Instructions for ssdeanx/ssd-ai, covering memory bank, memory bank structure, core files (required), additional context and core workflows.
flyto-core AGENTS.md
AGENTS.md instructions for flytohub/flyto-core, covering flyto-core agent rules, flyto2 project memory contract, flyto2 frontend quality gate and repo notes.
raindrop-mcp copilot-instructions.md
Instructions for adeze/raindrop-mcp: The canonical project instructions are in AGENTS.md. Follow them for architecture, MCP safety constraints, tooling, validation, and release policy.
obsidian-vault-mcp CLAUDE.md
Claude Code instructions for ebullient/obsidian-vault-mcp, covering obsidian vault mcp, code style and qa.
state-memory-mcp copilot-instructions.md
Instructions for putervision/state-memory-mcp, covering state memory (state-memory-mcp), 1. priority order, 2. when to write to the graph, 3. workflow pattern and 4. codebase seeding on initialization.