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/Durable-Technology/mcp-micromanage-your-agentWrote 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/durable-technology/mcp-micromanage-your-agent/task-status-update-rule)<a href="https://agentmods.dev/rules/durable-technology/mcp-micromanage-your-agent/task-status-update-rule"><img src="https://agentmods.dev/badge/rules/durable-technology/mcp-micromanage-your-agent/task-status-update-rule.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.00008 | $0.00267 |
| Opus 5 | $0.00004 | $0.00133 |
| Sonnet 5 | $0.00002 | $0.00053 |
| Haiku 4.5 | $0.00001 | $0.00027 |
Grade A, and why
task-status-update-rule 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-status-update-rule — 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.
What it actually says
**STRICT RULES - MUST BE FOLLOWED WITHOUT EXCEPTION:**
There is always exactly one task in either the in_progress or user_review state.
Before updating the status, we guarantee that each condition is met.
needsRefinment → in_progress conditions:
✅ Requirements have been sufficiently clarified and ready for implementation
✅ **Fully understand the code's dependencies and have already reviewed them**
✅ The impact on existing code has been assessed
in_progress → user_review conditions:
✅ I explicitly checked that there were no compile errors
✅ Necessary tests have been added and all pass
✅ Required documentation updates are completed
user_review → in_progress conditions:
✅ From feedback, the content to be modified is completely clear
**user_review → completed conditions**:
✅ Only when explicitly approved by the user, absolutely.
* → needsRefinment conditions:
✅ It becomes apparent that the task requirements are unclear or incomplete
* → cancelled conditions:
✅ There is a clear reason why the task is no longer needed, or alternative methods or solutions to meet the requirements are clear
✅ The impact of cancellation on other related tasks has been evaluated
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 · 31 lines · 8 tokens per session scan A ca7abb927bfe
task-status-update-rule is a cursor rule published in the GitHub repository Durable-Technology/mcp-micromanage-your-agent (1 stars, last pushed 1y ago), licensed MIT. It adds 8 tokens to every session and 267 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to task-status-update-rule, 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).