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 rules/ejsinfuego/memory-mcp/local-brain-mcp-usagegit clone --depth 1 https://github.com/ejsinfuego/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/rules/ejsinfuego/memory-mcp/local-brain-mcp-usage)<a href="https://agentmods.dev/rules/ejsinfuego/memory-mcp/local-brain-mcp-usage"><img src="https://agentmods.dev/badge/rules/ejsinfuego/memory-mcp/local-brain-mcp-usage.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.00963 | $0.00963 |
| Opus 5 | $0.00481 | $0.00481 |
| Sonnet 5 | $0.00193 | $0.00193 |
| Haiku 4.5 | $0.00096 | $0.00096 |
Grade A, and why
local-brain-mcp-usage 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 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.
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.
- 4d ago First seen · 42 lines · 963 tokens per session scan A 8e4d9c4f2f82
local-brain-mcp-usage is a cursor rule published in the GitHub repository ejsinfuego/memory-mcp (0 stars, last pushed 4mo ago), with no licence file. It adds 963 tokens to every session, about $0.0048 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-31.
Other cursor rules, from other repositories
cursor-rules
You have access to a persistent cross-session memory via the memory MCP server. Knowledge survives between sessions and is shared across agents working on the same project.
aictx
Cursor rule "aictx" from oldskultxo/aictx, covering aictx, priority model, default loop, inspection and advanced tools and what to record.
cursorrules
你是一个 ascript 自动化脚本开发助手。.
160-workflow-orchestration
WHEN executing tasks MANAGE workflow processes for consistent memory operations.
050-reference-verification-system
description: WHEN referencing memory files ENSURE references are verified for accuracy and relevance globs: ["/.md", "/.mdc"] alwaysApply: true.
801-python-environment
Cursor rule "801-python-environment" from savagelysubtle/BIG-BRAIN-Memory-Bank, covering first, activate the virtual environment, then use uv to install packages, bad: installing directly without environment activation and bad: using pip instead of uv.