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/issmirnov/ynab-mcp-server/memory-bankgit clone --depth 1 https://github.com/issmirnov/ynab-mcp-serverWrote 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/issmirnov/ynab-mcp-server/memory-bank)<a href="https://agentmods.dev/rules/issmirnov/ynab-mcp-server/memory-bank"><img src="https://agentmods.dev/badge/rules/issmirnov/ynab-mcp-server/memory-bank.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.1 | $0.01163 | $0.01163 |
| Opus 5 | $0.00581 | $0.00581 |
| Sonnet 5 | $0.00233 | $0.00233 |
| Haiku 4.5 | $0.00116 | $0.00116 |
Grade A, and why
memory-bank 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 5d 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
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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.
- 5d ago First seen · 162 lines · 1,163 tokens per session scan A 80f344e2565b
memory-bank is a cursor rule published in the GitHub repository issmirnov/ynab-mcp-server (2 stars, last pushed 28d ago), with no licence file. It adds 1,163 tokens to every session, about $0.0058 per session on Opus 5. A static security scan graded it A with 0 findings. It comes from a forked repository.
Other cursor rules, from other repositories
session-distill
How to distill a long work session into ContextForge so a fresh session can resume cleanly. Invoke when the user asks to distill/hand off/checkpoint the session, when context is getting bloated and work is unfinished, or before deliberately starting a new session on the same task.
synapse
Rules for using Synapse MCP — prefer the graph over grep.
vision-memory-mcp
This project utilizes vision-memory-mcp to cache visual states, record layout transitions, provide element grounding, and avoid repetitive LLM vision calls.
cursor
Sepia memory — MANDATORY recall before work, persist after. Always-on.
main
🚨 CRITICAL RULE: MEMORY BANK CREATION IS MANDATORY 🚨 Memory Bank MUST be created BEFORE any other operation in ANY mode NO process can continue without verifying Memory Bank existence.
memory-bank-paths
Defines canonical paths for core Memory Bank files.