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/angry-robot-deals/ace-mcp/quick-documentationgit 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/quick-documentation)<a href="https://agentmods.dev/rules/angry-robot-deals/ace-mcp/quick-documentation"><img src="https://agentmods.dev/badge/rules/angry-robot-deals/ace-mcp/quick-documentation.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.01469 | $0.01469 |
| Opus 5 | $0.00734 | $0.00734 |
| Sonnet 5 | $0.00294 | $0.00294 |
| Haiku 4.5 | $0.00147 | $0.00147 |
Grade A, and why
quick-documentation 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 5d 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 quick-documentation — 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 — 226 lines — stays where its author put it; the contents beside it link to each section on GitHub.
description: Quick documentation approach for Level 1 Quick Bug Fix tasks globs: "/level1/", "/documentation/" alwaysApply: false
QUICK DOCUMENTATION FOR LEVEL 1 TASKS
TL;DR: This document outlines a quick documentation approach for Level 1 (Quick Bug Fix) tasks, ensuring that essential information is captured with minimal overhead.
🔍 QUICK DOCUMENTATION OVERVIEW
graph TD
FixComplete["Bug Fix<br>Complete"] --> Document["Document<br>Solution"]
Document --> UpdateTasks["Update<br>tasks.md"]
UpdateTasks --> MinimalUpdates["Make Minimal<br>Memory Bank Updates"]
MinimalUpdates --> CrossReference["Create Simple<br>Cross-References"]
CrossReference --> Complete["Documentation<br>Complete"]
Level 1 tasks require efficient documentation that captures essential information without unnecessary detail. This approach ensures that critical knowledge is preserved while maintaining speed and efficiency.
📋 DOCUMENTATION PRINCIPLES
- Conciseness: Keep documentation brief but complete
- Focus: Document only what's necessary to understand the fix
- Context: Provide sufficient context to understand the issue
- Solution: Clearly describe what was changed and why
- Findability: Ensure the fix can be easily found later
📋 QUICK FIX DOCUMENTATION TEMPLATE
# Quick Fix: [Issue Title]
## Issue
[Brief description of the problem - 1-2 sentences]
## Root Cause
[Concise description of what caused the issue - 1-2 sentences]
## Solution
[Brief description of the fix implemented - 2-3 sentences]
## Files Changed
- [File path 1]
- [File path 2]
## Verification
[How the fix was tested/verified - 1-2 sentences]
## Notes
[Any additional information that might be helpful - optional]
📋 TASKS.MD UPDATES
For Level 1 tasks, update tasks.md with this format:
## Completed Bug Fixes
- [X] [Level 1] Fixed: [Issue title] (Completed: YYYY-MM-DD)
- Issue: [One-line description]
- Root Cause: [One-line description]
- Solution: [One-line description]
- Files: [File paths]
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.
- 5d ago First seen · 226 lines · 1,469 tokens per session scan A 3bd37f2bad7a
quick-documentation is a cursor rule published in the GitHub repository Angry-Robot-Deals/ace-mcp (4 stars, last pushed 6mo ago), licensed MIT. It adds 1,469 tokens to every session, about $0.0073 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to quick-documentation, differing in 0 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-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.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.