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-level3git 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-level3)<a href="https://agentmods.dev/rules/angry-robot-deals/ace-mcp/workflow-level3"><img src="https://agentmods.dev/badge/rules/angry-robot-deals/ace-mcp/workflow-level3.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.04362 |
| Opus 5 | $0.00000 | $0.02181 |
| Sonnet 5 | $0.00000 | $0.00872 |
| Haiku 4.5 | $0.00000 | $0.00436 |
Grade A, and why
workflow-level3 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
97% identical to workflow-level3 — 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 — 326 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LEVEL 3 WORKFLOW: INTERMEDIATE FEATURE DEVELOPMENT
TL;DR: This document outlines a structured workflow for Level 3 (Intermediate Feature) tasks. These tasks involve developing significant new functionality that may span multiple components, requiring comprehensive planning, often necessitating targeted creative design phases, followed by systematic implementation, in-depth reflection, and feature-specific archiving. This workflow balances detailed process with efficiency for moderately complex features.
🔍 LEVEL 3 WORKFLOW OVERVIEW
Level 3 tasks represent a significant development effort, building a complete feature. The workflow ensures adequate planning, design for key aspects, and methodical execution.
graph LR
Init["1. INITIALIZATION<br>(VAN Mode Output)"] -->
DocSetup["2. DOCUMENTATION SETUP"] -->
Plan["3. FEATURE PLANNING (PLAN Mode)"] -->
Creative["4. CREATIVE PHASES (CREATIVE Mode)"] -->
Impl["5. IMPLEMENTATION (IMPLEMENT Mode)"] -->
Reflect["6. REFLECTION (REFLECT Mode)"] -->
Archive["7. ARCHIVING (ARCHIVE Mode)"]
%% Document connections for each phase (conceptual links to mode guidance)
Init -.-> InitDocs["Core Rules & L3 Confirmation"]
DocSetup -.-> DocSetupDocs["Memory Bank Setup for L3"]
Plan -.-> PlanDocs["Comprehensive Feature Plan"]
Creative -.-> CreativeDocs["Targeted Design Documents"]
Impl -.-> ImplDocs["Feature Implementation & Testing"]
Reflect -.-> ReflectDocs["In-depth Feature Reflection"]
Archive -.-> ArchiveDocs["Feature Archive Package"]
style Init fill:#a1c4fd,stroke:#669df6
style DocSetup fill:#b3e5fc,stroke:#81d4fa
style Plan fill:#c8e6c9,stroke:#a5d6a7
style Creative fill:#ffd8b2,stroke:#ffcc80
style Impl fill:#ffcdd2,stroke:#ef9a9a
style Reflect fill:#d1c4e9,stroke:#b39ddb
style Archive fill:#cfd8dc,stroke:#b0bec5
Level 3 tasks typically involve creating a new, distinct feature or making substantial modifications to an existing one that affects multiple parts of the application.
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 · 326 lines · 0 tokens per session scan A 4f048ee96705
workflow-level3 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 4,362 tokens. A static security scan graded it A with 0 findings. It is 97% identical to workflow-level3, differing in 4 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-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
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.