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/task-tracking-intermediategit 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-intermediate)<a href="https://agentmods.dev/rules/angry-robot-deals/ace-mcp/task-tracking-intermediate"><img src="https://agentmods.dev/badge/rules/angry-robot-deals/ace-mcp/task-tracking-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 | $0.00000 | $0.01030 |
| Opus 5 | $0.00000 | $0.00515 |
| Sonnet 5 | $0.00000 | $0.00206 |
| Haiku 4.5 | $0.00000 | $0.00103 |
Grade A, and why
task-tracking-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 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 task-tracking-intermediate — 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 — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
LEVEL 3 INTERMEDIATE TASK TRACKING
TL;DR: This document provides structured task tracking guidelines for Level 3 (Intermediate Feature) tasks, using visual tracking elements and clear checkpoints.
🔍 TASK TRACKING WORKFLOW
graph TD
Start["Task Start"] --> Init["📋 Initialize<br>Task Entry"]
Init --> Struct["🏗️ Create Task<br>Structure"]
Struct --> Track["📊 Progress<br>Tracking"]
Track --> Update["🔄 Regular<br>Updates"]
Update --> Complete["✅ Task<br>Completion"]
Struct --> Components["Components:"]
Components --> Req["Requirements"]
Components --> Steps["Implementation<br>Steps"]
Components --> Creative["Creative Phase<br>Markers"]
Components --> Check["Checkpoints"]
Track --> Status["Track Status:"]
Status --> InProg["🔄 In Progress"]
Status --> Block["⛔ Blocked"]
Status --> Done["✅ Complete"]
Status --> Skip["⏭️ Skipped"]
style Start fill:#4da6ff,stroke:#0066cc,color:white
style Init fill:#ffa64d,stroke:#cc7a30,color:white
style Struct fill:#4dbb5f,stroke:#36873f,color:white
style Track fill:#d94dbb,stroke:#a3378a,color:white
style Update fill:#4dbbbb,stroke:#368787,color:white
style Complete fill:#d971ff,stroke:#a33bc2,color:white
📋 TASK ENTRY TEMPLATE
# [Task Title]
## Requirements
- [ ] Requirement 1
- [ ] Requirement 2
- [ ] Requirement 3
## Components Affected
- Component 1
- Component 2
- Component 3
## Implementation Steps
1. [ ] Step 1
2. [ ] Step 2
3. [ ] Step 3
## Creative Phases Required
- [ ] 🎨 UI/UX Design
- [ ] 🏗️ Architecture Design
- [ ] ⚙️ Algorithm Design
## Checkpoints
- [ ] Requirements verified
- [ ] Creative phases completed
- [ ] Implementation tested
- [ ] Documentation updated
## Current Status
- Phase: [Current Phase]
- Status: [In Progress/Blocked/Complete]
- Blockers: [If any]
🔄 PROGRESS TRACKING VISUALIZATION
graph TD
subgraph "TASK PROGRESS"
P1["✓ Requirements<br>Defined"]
P2["✓ Components<br>Identified"]
P3["→ Creative Phase<br>In Progress"]
P4["□ Implementation"]
P5["□ Testing"]
P6["□ Documentation"]
end
style P1 fill:#4dbb5f,stroke:#36873f,color:white
style P2 fill:#4dbb5f,stroke:#36873f,color:white
style P3 fill:#ffa64d,stroke:#cc7a30,color:white
style P4 fill:#d94dbb,stroke:#a3378a,color:white
style P5 fill:#4dbbbb,stroke:#368787,color:white
style P6 fill:#d971ff,stroke:#a33bc2,color:white
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 · 135 lines · 0 tokens per session scan A 2a82aa59872a
task-tracking-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,030 tokens. A static security scan graded it A with 0 findings. It is 100% identical to task-tracking-intermediate, differing in 0 lines, and is treated as a copy.
Other cursor rules, from other repositories
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.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.