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/archive-mode-map)<a href="https://agentmods.dev/rules/angry-robot-deals/ace-mcp/archive-mode-map"><img src="https://agentmods.dev/badge/rules/angry-robot-deals/ace-mcp/archive-mode-map/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/angry-robot-deals/ace-mcp/archive-mode-map"><img src="https://agentmods.dev/badge/rules/angry-robot-deals/ace-mcp/archive-mode-map.svg" alt="Reviewed on agentmods" width="80" 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.02071 |
| Opus 5 | $0.00000 | $0.01035 |
| Sonnet 5 | $0.00000 | $0.00414 |
| Haiku 4.5 | $0.00000 | $0.00207 |
Grade A, and why
archive-mode-map 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 9d 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 archive-mode-map — 9 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 — 273 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ARCHIVE MODE: TASK DOCUMENTATION PROCESS MAP
TL;DR: This visual map guides the ARCHIVE mode process, focusing on creating comprehensive documentation of the completed task, archiving relevant files, and updating the Memory Bank for future reference.
🧭 ARCHIVE MODE PROCESS FLOW
graph TD
Start["START ARCHIVE MODE"] --> ReadTasks["Read tasks.md<br>reflection.md and<br>progress.md"]
%% Initial Assessment
ReadTasks --> VerifyReflect{"Reflection<br>Complete?"}
VerifyReflect -->|"No"| ReturnReflect["Return to<br>REFLECT Mode"]
VerifyReflect -->|"Yes"| AssessLevel{"Determine<br>Complexity Level"}
%% Level-Based Archiving
AssessLevel -->|"Level 1"| L1Archive["LEVEL 1 ARCHIVING"]
AssessLevel -->|"Level 2"| L2Archive["LEVEL 2 ARCHIVING<br>Level2/archive-basic.mdc"]
AssessLevel -->|"Level 3"| L3Archive["LEVEL 3 ARCHIVING<br>Level3/archive-intermediate.mdc"]
AssessLevel -->|"Level 4"| L4Archive["LEVEL 4 ARCHIVING<br>Level4/archive-comprehensive.mdc"]
%% Level 1 Archiving (Minimal)
L1Archive --> L1Summary["Create Quick<br>Summary"]
L1Summary --> L1Task["Update<br>tasks.md"]
L1Task --> L1Complete["Mark Task<br>Complete"]
%% Level 2 Archiving (Basic)
L2Archive --> L2Summary["Create Basic<br>Archive Document"]
L2Summary --> L2Doc["Document<br>Changes"]
L2Doc --> L2Task["Update<br>tasks.md"]
L2Task --> L2Progress["Update<br>progress.md"]
L2Progress --> L2Complete["Mark Task<br>Complete"]
%% Level 3-4 Archiving (Comprehensive)
L3Archive & L4Archive --> L34Summary["Create Comprehensive<br>Archive Document"]
L34Summary --> L34Doc["Document<br>Implementation"]
L34Doc --> L34Creative["Archive Creative<br>Phase Documents"]
L34Creative --> L34Code["Document Code<br>Changes"]
L34Code --> L34Test["Document<br>Testing"]
L34Test --> L34Lessons["Summarize<br>Lessons Learned"]
L34Lessons --> L34Task["Update<br>tasks.md"]
L34Task --> L34Progress["Update<br>progress.md"]
L34Progress --> L34System["Update System<br>Documentation"]
L34System --> L34Complete["Mark Task<br>Complete"]
%% Completion
L1Complete & L2Complete & L34Complete --> CreateArchive["Create Archive<br>Document in<br>docs/archive/"]
CreateArchive --> UpdateActive["Update<br>activeContext.md"]
UpdateActive --> Reset["Reset for<br>Next Task"]
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.
- 9d ago First seen · 273 lines · 2,071 tokens per session scan A 4d50f763dff3
archive-mode-map 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 2,071 tokens. A static security scan graded it A with 0 findings. It is 100% identical to archive-mode-map, differing in 9 lines, and is treated as a copy.
Other cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.