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/Angry-Robot-Deals/ace-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/angry-robot-deals/ace-mcp/main)<a href="https://agentmods.dev/rules/angry-robot-deals/ace-mcp/main"><img src="https://agentmods.dev/badge/rules/angry-robot-deals/ace-mcp/main.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.00000 | $0.01423 |
| Opus 5 | $0.00000 | $0.00711 |
| Sonnet 5 | $0.00000 | $0.00285 |
| Haiku 4.5 | $0.00000 | $0.00142 |
Grade A, and why
main 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 7d 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.
This is a copy
100% identical to main — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 156 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🔍 ISOLATION-FOCUSED MEMORY BANK SYSTEM
🚨 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
TL;DR: This system is designed to work with Cursor custom modes, where each mode loads only the rules it needs. The system uses visual Mermaid diagrams and selective document loading to optimize context usage.
🧭 MODE-SPECIFIC VISUAL MAPS
graph TD
subgraph Modes["Cursor Custom Modes"]
VAN["VAN MODE<br>Initialization"] --> PLAN["PLAN MODE<br>Task Planning"]
PLAN --> Creative["CREATIVE MODE<br>Design Decisions"]
Creative --> Implement["IMPLEMENT MODE<br>Code Implementation"]
Implement --> Reflect["REFLECT MODE<br>Task Review"]
Reflect --> Archive["ARCHIVE MODE<br>Documentation"]
end
VAN -.->|"Loads"| VANRules["• main.md<br>• platform-awareness.md<br>• file-verification.md<br>• workflow-init.md"]
PLAN -.->|"Loads"| PLANRules["• main.md<br>• task-tracking.md<br>• planning-process.md"]
Creative -.->|"Loads"| CreativeRules["• main.md<br>• creative-phase.md<br>• design-patterns.md"]
Implement -.->|"Loads"| ImplementRules["• main.md<br>• command-execution.md<br>• implementation-guide.md"]
Reflect -.->|"Loads"| ReflectRules["• main.md<br>• reflection-format.md"]
Archive -.->|"Loads"| ArchiveRules["• main.md<br>• archiving-guide.md"]
📋 MEMORY BANK VERIFICATION - MANDATORY IN ALL MODES
graph TD
Start["Mode Activation"] --> CheckMemBank{"Memory Bank<br>Exists?"}
CheckMemBank -->|"No"| CreateMemBank["CREATE MEMORY BANK<br>[CRITICAL STEP]"]
CheckMemBank -->|"Yes"| VerifyMemBank["Verify Memory Bank<br>Structure"]
CreateMemBank --> VerifyCreation{"Creation<br>Successful?"}
VerifyCreation -->|"No"| AbortAll["⛔ ABORT ALL OPERATIONS<br>Fix Memory Bank First"]
VerifyCreation -->|"Yes"| VerifyMemBank
VerifyMemBank --> StructureCheck{"Structure<br>Valid?"}
StructureCheck -->|"No"| FixStructure["Fix Memory Bank<br>Structure"]
StructureCheck -->|"Yes"| ContinueMode["Continue with<br>Mode Operations"]
FixStructure --> VerifyFix{"Fix<br>Successful?"}
VerifyFix -->|"No"| AbortAll
VerifyFix -->|"Yes"| ContinueMode
style CheckMemBank fill:#ff0000,stroke:#990000,color:white,stroke-width:3px
style CreateMemBank fill:#ff0000,stroke:#990000,color:white,stroke-width:3px
style VerifyCreation fill:#ff0000,stroke:#990000,color:white,stroke-width:3px
style AbortAll fill:#ff0000,stroke:#990000,color:white,stroke-width:3px
style StructureCheck fill:#ff0000,stroke:#990000,color:white,stroke-width:3px
style FixStructure fill:#ff5555,stroke:#dd3333,color:white
style VerifyFix fill:#ff5555,stroke:#dd3333,color:white
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.
- 7d ago First seen · 156 lines · 0 tokens per session scan A 87d33e5b0668
main is a cursor rule published in the GitHub repository Angry-Robot-Deals/ace-mcp (4 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,423 tokens. A static security scan graded it A with 0 findings. It is 100% identical to main, differing in 0 lines, and is treated as a copy.
Other cursor rules, from other repositories
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…
context-recorder-system
A modular system for recording project context, decisions, requirements, and lessons in structured files. It divides the recorder into core, template, advanced, and edge-case modules.
self-improving-obsidian-llm-wiki
LLM Wiki OS operating rules.