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/the-focus-ai/buttondown-mcp/cursorrulesgit 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/cursorrules)<a href="https://agentmods.dev/rules/the-focus-ai/buttondown-mcp/cursorrules"><img src="https://agentmods.dev/badge/rules/the-focus-ai/buttondown-mcp/cursorrules.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.00266 | $0.00266 |
| Opus 5 | $0.00133 | $0.00133 |
| Sonnet 5 | $0.00053 | $0.00053 |
| Haiku 4.5 | $0.00027 | $0.00027 |
Grade A, and why
cursorrules 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 3d 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.
What it actually says
Cursor Memories and Preferences
This file stores important memories and preferences that should be remembered across sessions. It is automatically updated whenever the user says "remember" something.
Structure
Each memory or preference is stored with:
- Date added
- Category
- Content
- Context (if relevant)
Memories
Project-Specific
- [No memories yet]
User Preferences
- Date: 2024-03-26 Category: Package Manager Content: Always use pnpm as the package manager Context: This is the preferred package manager for all Node.js projects
Technical Decisions
- Date: 2024-03-26 Category: API Development Content: When building an API, always directly hit the API and store the results in a directory, and then build the types based upon the results Context: This approach ensures type definitions are based on actual API responses rather than theoretical structures
Workflow Patterns
- [No patterns yet]
How to Use
When the user says "remember" something:
- Add the new memory/preference to the appropriate section
- Include the date it was added
- Add any relevant context
- Format it clearly for future reference
Last Updated
2024-03-26
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.
- 3d ago First seen · 50 lines · 266 tokens per session scan A a640314d1bfd
cursorrules is a cursor rule published in the GitHub repository The-Focus-AI/buttondown-mcp (1 stars, last pushed 1y ago), licensed MIT. It adds 266 tokens to every session, about $0.0013 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…