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/maingit 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/main)<a href="https://agentmods.dev/rules/moclam1905/cocktailrecipes/main"><img src="https://agentmods.dev/badge/rules/moclam1905/cocktailrecipes/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 | $0.00000 | $0.01075 |
| Opus 5 | $0.00000 | $0.00537 |
| Sonnet 5 | $0.00000 | $0.00215 |
| Haiku 4.5 | $0.00000 | $0.00108 |
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 4d 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
🔍 ISOLATION-FOCUSED MEMORY BANK SYSTEM
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"]
📚 VISUAL PROCESS MAPS
Each mode has its own visual process map:
🔄 FILE STATE VERIFICATION
In this isolation-focused approach, Memory Bank files maintain continuity between modes:
graph TD
subgraph "Memory Bank Files"
tasks["tasks.md<br>Source of Truth"]
active["activeContext.md<br>Current Focus"]
creative["creative-*.md<br>Design Decisions"]
progress["progress.md<br>Implementation Status"]
end
VAN["VAN MODE"] -->|"Creates/Updates"| tasks
VAN -->|"Creates/Updates"| active
PLAN["PLAN MODE"] -->|"Reads"| tasks
PLAN -->|"Reads"| active
PLAN -->|"Updates"| tasks
Creative["CREATIVE MODE"] -->|"Reads"| tasks
Creative -->|"Creates"| creative
Creative -->|"Updates"| tasks
Implement["IMPLEMENT MODE"] -->|"Reads"| tasks
Implement -->|"Reads"| creative
Implement -->|"Updates"| tasks
Implement -->|"Updates"| progress
Reflect["REFLECT MODE"] -->|"Reads"| tasks
Reflect -->|"Reads"| progress
Reflect -->|"Updates"| tasks
Archive["ARCHIVE MODE"] -->|"Reads"| tasks
Archive -->|"Reads"| progress
Archive -->|"Archives"| creative
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.
- 4d ago First seen · 123 lines · 0 tokens per session scan A 5b57c0b12670
main 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 1,075 tokens. 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
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.
ai-assisted-development
AI-Assisted Development: prompt structure, context management, iterative refinement.
cpp
C++: modern patterns, memory safety, RAII.
00-workflow
Before responding to any request, call getsessioncontext.
resume
Resume from last checkpoint with state drift detection — validate persisted assumptions before continuing.