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.
git clone --depth 1 https://github.com/The-Focus-AI/buttondown-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/the-focus-ai/buttondown-mcp/memory-bank)<a href="https://agentmods.dev/rules/the-focus-ai/buttondown-mcp/memory-bank"><img src="https://agentmods.dev/badge/rules/the-focus-ai/buttondown-mcp/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.01608 | $0.01608 |
| Opus 5 | $0.00804 | $0.00804 |
| Sonnet 5 | $0.00322 | $0.00322 |
| Haiku 4.5 | $0.00161 | $0.00161 |
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 8d 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 — 196 lines — stays where its author put it; the contents beside it link to each section on GitHub.
STRICT RULES:
- ALWAYS FETCH ALL OF THE RULES
- Follow the rules instructions each every interaction!!!
- DON'T BE LAZY AND BE ATTENTIVE! AND DON'T GET HALLUCINATIONS, BE CONSISTENT!
- search codebase first, then write code
- Ensure code is complete! Verify thoroughly finalized.
- If you think there might not be a correct answer, you say so.
- always cross reference @tech-context.md @active-context.md @tech-context.md and @progress.md and @lessons-learned.md
- at the end of each interaction, look for relavent information and keep @tech-context.md @active-context.md @tech-context.md and @progress.md @lessons-learned.md
- when making a time stamp run the date command to get the current time
Core files
- Progress Tracking Rules:
- Use ONLY these markers: [X] = Completed (100% done, verified) [-] = In Progress (actively being worked on) [ ] = Planned (not started) [!] = Blocked (has dependencies) [?] = Needs Review (requires verification)
memory/project-brief.md
- Comprehensive document describing what we are building
- If the @project-brief.md doesn't exist, ask the use if they want to run the [Project Briefing Task]
memory/project-plan.md
- Contains the iterative steps to make project
- Mark status
memory/product-context.md
- Why this project exists
- Problems it solves
- How it should work
- User experience goals
- This will be helpful in updating the documentation
memory/tech-context.md
- Technology Used
- Development Setup
- Technical Contraints
- Depedancies
memory/active-context.md
- Current work focus
- Recent changes
- Next steps
- Active decisions and considerations
- Current chunk being implemented
- Progress through the project plan
- mark status
memory/lessons-learned.md
- History of lessons that we've learned during this project
memory/progress.md
- what works
- what is left to build
- current status
- known issues
memory/work-log.md
- Updated after each interaction with the user
Relationships
flowchart TD
PB[project-brief.md] --> PC[project-context.md]
PB --> TC[tech-context.md]
PB --> PP[project-plan.md]
PB --> AC[active-context.md]
TC --> AC
PP --> AC
AC --> PG[progress.md]
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.
- 8d ago First seen · 196 lines · 1,608 tokens per session scan A 4322d0c64b8e
memory-bank is a cursor rule published in the GitHub repository The-Focus-AI/buttondown-mcp (1 stars, last pushed 1y ago), licensed MIT. It adds 1,608 tokens to every session, about $0.0080 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
memory
Cursor rule "memory" from The-Focus-AI/plausible-mcp, covering important rules, strict rules, workflows, formating and core files.
project-overview
This project is Context Compose, a TypeScript-based package that provides Model Context Protocol (MCP) server and CLI tools. This tool is for AI-assisted development context management, so I want to ensure the assets contribute meaningfully to the project's purpose. I'll need to carefully analyze each file's role to…
mempalace-recall-always
Always-on MemPalace recall — search the palace before answering about past work, people, projects, or prior decisions.
dreamd-recall
Recall lessons, decisions, and prior context from the .agent/ memory daemon. Use when starting work in a project that has a .agent/ folder, when the user references a past decision, or when you are about to make a choice that has a documented prior.
session-memory
Use at conversation wrap-up or when the user explicitly indicates end-of-session — capture residual lessons not captured in-flight.
common_memory_bank
I am Cursor, an expert software engineer with a unique characteristic: my memory resets completely between sessions. This isn't a limitation - it's what drives me to maintain perfect documentation. After each reset, I rely ENTIRELY on my Memory Bank to understand the project and continue work effectively. I MUST read…