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/workflow-level4git 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/workflow-level4)<a href="https://agentmods.dev/rules/angry-robot-deals/ace-mcp/workflow-level4"><img src="https://agentmods.dev/badge/rules/angry-robot-deals/ace-mcp/workflow-level4.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.03729 | $0.03729 |
| Opus 5 | $0.01865 | $0.01865 |
| Sonnet 5 | $0.00746 | $0.00746 |
| Haiku 4.5 | $0.00373 | $0.00373 |
Grade A, and why
workflow-level4 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 workflow-level4 — 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 — 424 lines — stays where its author put it; the contents beside it link to each section on GitHub.
description: Comprehensive workflow for Level 4 Complex System tasks globs: "/level4/", "/workflow/" alwaysApply: false
COMPREHENSIVE WORKFLOW FOR LEVEL 4 TASKS
TL;DR: This document outlines a comprehensive workflow for Level 4 (Complex System) tasks, including 7 key phases with rigorous planning, mandatory creative phases, architectural design, phased implementation, and extensive documentation.
🔍 LEVEL 4 WORKFLOW OVERVIEW
graph LR
Init["1. INITIALIZATION"] --> Doc["2. DOCUMENTATION<br>SETUP"]
Doc --> Plan["3. ARCHITECTURAL<br>PLANNING"]
Plan --> Create["4. CREATIVE<br>PHASES"]
Create --> Impl["5. PHASED<br>IMPLEMENTATION"]
Impl --> Reflect["6. REFLECTION"]
Reflect --> Archive["7. ARCHIVING"]
%% Document connections for each phase
Init -.-> InitDocs["INITIALIZATION"]
Doc -.-> DocDocs["DOCUMENTATION"]
Plan -.-> PlanDocs["ARCHITECTURAL PLANNING"]
Create -.-> CreateDocs["CREATIVE PHASES"]
Impl -.-> ImplDocs["PHASED IMPLEMENTATION"]
Reflect -.-> ReflectDocs["REFLECTION"]
Archive -.-> ArchiveDocs["ARCHIVING"]
🔄 LEVEL TRANSITION HANDLING
graph TD
L4["Level 4 Task"] --> Assess["Continuous<br>Assessment"]
Assess --> Down["Downgrade to<br>Level 2/3"]
Assess --> Split["Split into<br>Multiple Tasks"]
Down --> L23Trigger["Triggers:<br>- Less complex<br>- Limited scope<br>- Few components"]
Split --> MultiTrigger["Triggers:<br>- Too large<br>- Independent parts<br>- Parallel possible"]
L23Trigger --> L23Switch["Switch to<br>Level 2/3 Workflow"]
MultiTrigger --> CreateTasks["Create Multiple<br>Lower Level Tasks"]
Level 4 tasks involve complex systems that require comprehensive planning, rigorous design, systematic implementation, and thorough documentation. This workflow ensures all aspects are addressed with the appropriate level of detail, structure, and verification.
📋 WORKFLOW PHASES
Phase 1: INITIALIZATION
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 · 424 lines · 3,729 tokens per session scan A 9b57eef061ff
workflow-level4 is a cursor rule published in the GitHub repository Angry-Robot-Deals/ace-mcp (4 stars, last pushed 6mo ago), licensed MIT. It adds 3,729 tokens to every session, about $0.0186 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to workflow-level4, 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.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.