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/yodakeisuke/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/yodakeisuke/mcp-micromanage-your-agent/task-status-update-rule)<a href="https://agentmods.dev/rules/yodakeisuke/mcp-micromanage-your-agent/task-status-update-rule"><img src="https://agentmods.dev/badge/rules/yodakeisuke/mcp-micromanage-your-agent/task-status-update-rule/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/yodakeisuke/mcp-micromanage-your-agent/task-status-update-rule"><img src="https://agentmods.dev/badge/rules/yodakeisuke/mcp-micromanage-your-agent/task-status-update-rule.svg" alt="Reviewed on agentmods" width="80" 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 9d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- task-status-update-rule — 100% identical, 0 lines differ
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.
- 9d 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 yodakeisuke/mcp-micromanage-your-agent (13 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. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other cursor rules, from other repositories
md-feedback-workflow
This project uses md-feedback for structured human review of implementation plans.
project-epic-template-cursorrules-prompt-file
Cursor rules for project development with epic template integration.
bootstrap-alwayson
Minimal always-required LLM fixes.
client-workflow-bootstrap
Cursor rule "client-workflow-bootstrap" from ulises-jeremias/agent-toolkit, covering agent vs skill rule — why agent (cite clause), when to use vs holistic, caller / skills / handoff, interview process and gate before generating.
tasks
Guidelines for implementing task management operations.
taskmaster
Comprehensive reference for Taskmaster MCP tools and CLI commands.