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-intermediate)<a href="https://agentmods.dev/rules/angry-robot-deals/ace-mcp/archive-intermediate"><img src="https://agentmods.dev/badge/rules/angry-robot-deals/ace-mcp/archive-intermediate.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.01133 |
| Opus 5 | $0.00000 | $0.00566 |
| Sonnet 5 | $0.00000 | $0.00227 |
| Haiku 4.5 | $0.00000 | $0.00113 |
Grade A, and why
archive-intermediate 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 8d 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
95% identical to archive-intermediate β 4 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 β 79 lines β stays where its author put it; the contents beside it link to each section on GitHub.
LEVEL 3 ARCHIVE: INTERMEDIATE FEATURE DOCUMENTATION
TL;DR: This guide outlines the archiving process for a completed Level 3 intermediate feature. The aim is to create a self-contained, easily accessible record of the feature's development lifecycle, including its planning, design decisions, implementation summary, and reflection.
π Before You Start Archiving (L3 Pre-Archive Checklist)
- Confirm Reflection Complete: Verify in
memory-bank/tasks.mdthat the reflection phase for this feature is marked as complete andmemory-bank/reflection-[feature_id].mdexists and is finalized. - Gather All Feature-Specific Documents:
- The feature plan section from
memory-bank/tasks.md(or a copy of it). - All
memory-bank/creative/creative-[aspect_name].mddocuments related to this feature. - The
memory-bank/reflection/reflection-[feature_id].mddocument. - Key diagrams or architectural notes from
memory-bank/progress.mdif not captured elsewhere. - A link to the primary commit(s) or feature branch merge for the implemented code.
- The feature plan section from
π¦ Level 3 Archiving Workflow
graph TD
StartArchive["Start L3 Archiving"] -->
VerifyReflect["1. Verify Reflection Complete<br>Check `tasks.md` & `reflection-[feature_id].md`"] -->
GatherDocs["2. Gather All Feature Documents<br>(Plan, Creative outputs, Reflection, Code links)"] -->
CreateArchiveFile["3. Create Feature Archive File<br>e.g., `doc/archive/feature-[FeatureNameOrID]_YYYYMMDD.md`"] -->
PopulateArchive["4. Populate Archive File<br>(Using L3 Archive Template below)"] -->
VerifyLinks["5. Verify All Internal Links<br>in Archive File are Correct"] -->
FinalUpdateTasks["6. Final Update to `tasks.md`<br>(Mark Feature FULLY COMPLETED & ARCHIVED, link to archive file)"] -->
UpdateProgressFile["7. Add Final Entry to `progress.md`<br>(Note archiving & link to archive file)"] -->
ClearActiveCtx["8. Clear `activeContext.md`<br>Reset for Next Task/Project"] -->
ArchiveDone["L3 Archiving Complete<br>Feature successfully documented and closed."]
style StartArchive fill:#90a4ae,stroke:#607d8b
style ArchiveDone fill:#b0bec5,stroke:#90a4ae
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.
- 8d ago First seen Β· 79 lines Β· 0 tokens per session scan A 03cfb5860633
archive-intermediate 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,133 tokens. A static security scan graded it A with 0 findings. It is 95% identical to archive-intermediate, differing in 4 lines, and is treated as a copy.
Other cursor rules, from other repositories
slice-tasks
PLANNING SPINE STEP 2 of 3 β Slice the work: break a scoped PRD into vertical-slice stories in specs/epics/. Use after scope-work (step 1), before plan-work (step 3). Not a substitute for scope-work or plan-work.
iris
GitHub operations specialist β branches, pull requests, issues, releases, tags. Called by zeus after review. Never pushes or merges without explicit human approval. Integrates with VS Code GitHub Pull Requests extension.
elite-orchestrator
Elite orchestrator for mission-critical, enterprise-scale tasks requiring strategic coordination of 7+ agents across all domains. Makes architectural decisions, manages risk, ensures business continuity, and delivers enterprise-grade outcomes. Use for platform migrations, security incidents, multi-system integrationsβ¦
feedback-enhanced
Rules for an interactive feedback system that lets users and an AI agent discuss complex development work in real time. It includes guidance for recording decisions, tracking progress and handling detailed inputs such as code and diagrams.
project-onboarding-rule
Automatically onboards existing projects into the AI-driven development workflow.
linear-in-review
After finishing a Linear issue, set its status to In Review (never Done).