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/jondoescoding/jondoescoding-coding-rulesWrote 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/jondoescoding/jondoescoding-coding-rules/task-management)<a href="https://agentmods.dev/rules/jondoescoding/jondoescoding-coding-rules/task-management"><img src="https://agentmods.dev/badge/rules/jondoescoding/jondoescoding-coding-rules/task-management/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/jondoescoding/jondoescoding-coding-rules/task-management"><img src="https://agentmods.dev/badge/rules/jondoescoding/jondoescoding-coding-rules/task-management.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.00000 | $0.01705 |
| Opus 5.5 | $0.00000 | $0.00682 |
| Sonnet 5.5 | $0.00000 | $0.00341 |
| Haiku 4.5 | $0.00000 | $0.00170 |
Grade A, and why
task-management 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 1mo 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 — 202 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Task Management System
Overview
This rule defines the standard format and workflow for task generation, tracking, and management.
CRITICAL CONTEXT: The person we are developing for has dementia and desperately needs to understand what is going on. All task documentation must be extremely clear, detailed, and provide complete context at every step. Use simple language, detailed explanations, and frequent status updates to ensure full comprehension.
Required Template Structure
1. Main Goal Section
## 🎯 MAIN GOAL (Read This First!)
[Clear, simple explanation of what we want to accomplish]
2. Key Things to Remember Section (CRITICAL - Always Include This First!)
## 🔑 KEY THINGS TO REMEMBER
### ❌ DON'Ts (Things to Avoid)
- **DON'T [specific action]** - [clear explanation of why not]
- **DON'T [specific action]** - [clear explanation of why not]
- **DON'T [specific action]** - [clear explanation of why not]
### ✅ DOs (Things to Do)
- **DO [specific action]** - [clear explanation of what to do]
- **DO [specific action]** - [clear explanation of what to do]
- **DO [specific action]** - [clear explanation of what to do]
### 📝 Notes
- **[Important concept]**: [detailed explanation]
- **[Important concept]**: [detailed explanation]
- **[Performance/Efficiency Notes]**: [specific metrics or improvements expected]
3. Visual Flow Diagram Section
## 📊 Visual Flow Diagram
```mermaid
graph TD
A[Start Point] --> B[Next Step]
B --> C[Final Step]
style A fill:#e1f5fe
style B fill:#fff3e0
style C fill:#f3e5f5
### 4. Complete Task List Section
```markdown
## 📝 COMPLETE TASK LIST (Do These In Order!)
### 🔧 [CATEGORY NAME] ([Description])
#### ✅ Task 1: [Task Name] ([Order Description])
- **📁 File to Edit**: `path/to/file`
- **🎯 What to Find**: [What to look for]
- **✏️ What to Do**: [Specific actions]
- **📋 Specific [Items] to [Action]** (Copy this list):
item1 item2 item3
- **💡 Remember**: [Key reminder about this task]
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.
- 1mo ago First seen · 202 lines · 0 tokens per session scan A ed3bc997e3a4
task-management is a cursor rule published in the GitHub repository jondoescoding/jondoescoding-coding-rules (2 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,705 tokens. 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
_project
Project-wide conventions and developer environment context (RN monorepo, no-Mac dev).
dev_workflow
Guide for using Taskmaster to manage task-driven development workflows.
tasks
Guidelines for implementing task management operations.
dependencies
Guidelines for managing task dependencies and relationships.
tags
This document outlines the standardized patterns that ALL Task Master commands must follow to properly support the tagged task lists system.
taskmaster
Comprehensive reference for Taskmaster MCP tools and CLI commands.