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/davidl71/project-management-automation/task-status-standardizationgit clone --depth 1 https://github.com/davidl71/project-management-automationWrote 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/davidl71/project-management-automation/task-status-standardization)<a href="https://agentmods.dev/rules/davidl71/project-management-automation/task-status-standardization"><img src="https://agentmods.dev/badge/rules/davidl71/project-management-automation/task-status-standardization.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.00799 | $0.00799 |
| Opus 5 | $0.00400 | $0.00400 |
| Sonnet 5 | $0.00160 | $0.00160 |
| Haiku 4.5 | $0.00080 | $0.00080 |
Grade A, and why
task-status-standardization 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 3d 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.
How it starts
The opening of the file, as written. The whole thing — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Task Status Standardization Rules
🚨 CRITICAL: Always Use Title Case for Task Status
All Exarp tools MUST normalize task status to Title Case before updating.
Standard Status Values
✅ CORRECT (Title Case):
"Todo"(not "todo", "TODO", "pending")"In Progress"(not "in_progress", "in-progress", "In Progress")"Review"(not "review", "Review")"Done"(not "done", "DONE", "completed")
Required Pattern
ALWAYS use normalize_status_to_title_case() before setting status:
from project_management_automation.utils.todo2_utils import normalize_status_to_title_case
# ✅ CORRECT
task['status'] = normalize_status_to_title_case('done') # → "Done"
task['status'] = normalize_status_to_title_case('in_progress') # → "In Progress"
task['status'] = normalize_status_to_title_case('todo') # → "Todo"
# ❌ WRONG
task['status'] = 'done' # Will create inconsistency
task['status'] = 'in_progress' # Wrong format
task['status'] = 'Todo' # OK but not normalized
Where to Apply
MUST normalize status in:
- ✅
update_todos_mcp()- Already updated - ✅
_update_task_status()in automation base - Already updated - ✅ Direct file writes - Use normalization
- ✅ Status updates in tools - Use normalization
- ✅ Task creation - Use normalization
Enforcement
Before ANY status update:
- Import:
from project_management_automation.utils.todo2_utils import normalize_status_to_title_case - Normalize:
status = normalize_status_to_title_case(raw_status) - Use normalized value
Status normalization function:
- Location:
project_management_automation/utils/todo2_utils.py - Function:
normalize_status_to_title_case(status: str) -> str - Handles: All case variants, aliases (done→Done, completed→Done), spaces/underscores
Examples
Tool Updates:
# ✅ CORRECT
updates = [{
'id': task_id,
'status': normalize_status_to_title_case('done')
}]
update_todos_mcp(updates)
# ❌ WRONG
updates = [{'id': task_id, 'status': 'done'}] # Will be normalized by update_todos_mcp, but inconsistent
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.
- 3d ago First seen · 102 lines · 799 tokens per session scan A 24a5c59f4eaf
task-status-standardization is a cursor rule published in the GitHub repository davidl71/project-management-automation (1 stars, last pushed 6mo ago), licensed MIT. It adds 799 tokens to every session, about $0.0040 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-31.
Other cursor rules, from other repositories
development-workflow
AAMAD modular development workflow for context-aware agent coordination.
checkpoint
Write a committed handoff checkpoint so a fresh session can resume with zero loss. Use when crossing the 40% context line, on every stage transition, and at session end. Writes .trace/checkpoints/ - .md while the agent is still sharp.
feedback-enhanced
Enhanced feedback mechanism with 1-hour timeout - 增强反馈机制,1小时超时.
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).
sprint-planning
BMAD BMM Agent: sprint-planning.