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/moclam1905/cocktailrecipes/archive-mode-mapgit clone --depth 1 https://github.com/moclam1905/CocktailRecipesWrote 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/moclam1905/cocktailrecipes/archive-mode-map)<a href="https://agentmods.dev/rules/moclam1905/cocktailrecipes/archive-mode-map"><img src="https://agentmods.dev/badge/rules/moclam1905/cocktailrecipes/archive-mode-map.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.02089 |
| Opus 5 | $0.00000 | $0.01045 |
| Sonnet 5 | $0.00000 | $0.00418 |
| Haiku 4.5 | $0.00000 | $0.00209 |
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 6d 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 — 5 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 — 277 lines — stays where its author put it; the contents beside it link to each section on GitHub.
description: Visual process map for ARCHIVE mode (Task Documentation) globs: "/archive*/", "/document*/", "/complete*/" alwaysApply: false
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<br>Level1/archive-minimal.md"]
AssessLevel -->|"Level 2"| L2Archive["LEVEL 2 ARCHIVING<br>Level2/archive-basic.md"]
AssessLevel -->|"Level 3"| L3Archive["LEVEL 3 ARCHIVING<br>Level3/archive-standard.md"]
AssessLevel -->|"Level 4"| L4Archive["LEVEL 4 ARCHIVING<br>Level4/archive-comprehensive.md"]
%% 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.
- 6d ago First seen · 277 lines · 0 tokens per session scan A ff40f4ab922e
archive-mode-map is a cursor rule published in the GitHub repository moclam1905/CocktailRecipes (1 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,089 tokens. A static security scan graded it A with 0 findings. It is 100% identical to archive-mode-map, differing in 5 lines, and is treated as a copy.
Other cursor rules, from other repositories
workflow-memory
Workflow memory operating loop — read root state before acting, write state back after meaningful change.
ai-context-management
Rule Name: ai-context-management Description: When the conversation context is getting long or the model is losing track of details, proactively summarize and restructure context.
00-workflow
Before responding to any request, call getsessioncontext.
resume
Resume from last checkpoint with state drift detection — validate persisted assumptions before continuing.
checkpoint
Save a session checkpoint — what was done, what's next, blockers.
note
Quick note — save a thought, decision, or observation to session memory.