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/task-tracking-advanced)<a href="https://agentmods.dev/rules/angry-robot-deals/ace-mcp/task-tracking-advanced"><img src="https://agentmods.dev/badge/rules/angry-robot-deals/ace-mcp/task-tracking-advanced.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.04312 | $0.04312 |
| Opus 5 | $0.02156 | $0.02156 |
| Sonnet 5 | $0.00862 | $0.00862 |
| Haiku 4.5 | $0.00431 | $0.00431 |
Grade A, and why
task-tracking-advanced 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 7d 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 task-tracking-advanced β 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 β 466 lines β stays where its author put it; the contents beside it link to each section on GitHub.
description: Advanced task tracking for Level 4 Complex System tasks globs: "/level4/", "/task-tracking/" alwaysApply: false
ADVANCED TASK TRACKING FOR LEVEL 4 TASKS
TL;DR: This document outlines a comprehensive task tracking approach for Level 4 (Complex System) tasks, ensuring detailed tracking of complex, multi-phase work with clear dependencies, progress tracking, and architectural alignment.
π ADVANCED TASK TRACKING OVERVIEW
Level 4 Complex System tasks require sophisticated task tracking to manage the complexity of system development, coordinate multiple team members, track dependencies, and ensure alignment with architectural principles. This document outlines a comprehensive task tracking approach for such complex endeavors.
flowchart TD
classDef phase fill:#f9d77e,stroke:#d9b95c,color:#000
classDef artifact fill:#f4b8c4,stroke:#d498a4,color:#000
classDef verification fill:#c5e8b7,stroke:#a5c897,color:#000
Start([Begin Task<br>Tracking]) --> Framework[Establish Task<br>Framework]
Framework --> Hierarchy[Define Task<br>Hierarchy]
Hierarchy --> Breakdown[Create Work<br>Breakdown Structure]
Breakdown --> Dependencies[Document<br>Dependencies]
Dependencies --> Milestones[Define Key<br>Milestones]
Milestones --> Schedule[Create<br>Schedule]
Schedule --> Resources[Define Resource<br>Allocation]
Resources --> Risks[Document<br>Risks]
Risks --> Quality[Define Quality<br>Metrics]
Quality --> Progress[Track<br>Progress]
Progress --> Adaptations[Document<br>Adaptations]
Adaptations --> Verification{Task Tracking<br>Verification}
Verification -->|Pass| Complete([Task Tracking<br>Complete])
Verification -->|Fail| Revise[Revise Task<br>Tracking]
Revise --> Verification
Framework -.-> TF((Task<br>Framework))
Hierarchy -.-> TH((Task<br>Hierarchy))
Breakdown -.-> WBS((Work Breakdown<br>Structure))
Dependencies -.-> DP((Dependency<br>Matrix))
Milestones -.-> MS((Milestone<br>Document))
Schedule -.-> SC((Schedule<br>Document))
Resources -.-> RA((Resource<br>Allocation))
Risks -.-> RM((Risk<br>Management))
Quality -.-> QM((Quality<br>Metrics))
Progress -.-> PT((Progress<br>Tracking))
Adaptations -.-> AD((Adaptation<br>Document))
class Start,Complete milestone
class Framework,Hierarchy,Breakdown,Dependencies,Milestones,Schedule,Resources,Risks,Quality,Progress,Adaptations,Revise step
class Verification verification
class TF,TH,WBS,DP,MS,SC,RA,RM,QM,PT,AD artifact
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.
- 7d ago First seen Β· 466 lines Β· 4,312 tokens per session scan A bc27ff46de4b
task-tracking-advanced is a cursor rule published in the GitHub repository Angry-Robot-Deals/ace-mcp (4 stars, last pushed 6mo ago), licensed MIT. It adds 4,312 tokens to every session, about $0.0216 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to task-tracking-advanced, differing in 0 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).