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/kfnzero/mantis-mcp-server/task-trackinggit clone --depth 1 https://github.com/kfnzero/mantis-mcp-serverWhat 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.02597 |
| Opus 5 | $0.00000 | $0.01299 |
| Sonnet 5 | $0.00000 | $0.00519 |
| Haiku 4.5 | $0.00000 | $0.00260 |
Grade A, and why
task-tracking 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 2d 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-tracking — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 394 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ADAPTIVE TASK TRACKING PROTOCOL
TL;DR: Use tasks.md as the SINGLE SOURCE OF TRUTH for all task tracking. The task tracking process scales based on task complexity from Level 1 (quick bug fixes) to Level 4 (complex systems).
🚨 SINGLE SOURCE OF TRUTH RULE
Tasks.md is the ONLY file that should contain task status tracking:
- Use [ ] for pending tasks
- Use [X] for completed tasks
📝 TASKS.MD STRUCTURE
# Project Tasks
## Current Tasks
- [ ] Task 1: Description and details
- [ ] Subtask 1.1
- [ ] Subtask 1.2
- [ ] Task 2: Description and details
## Completed Tasks
- [X] Task 3: Completed on YYYY-MM-DD
- [X] Task 4: Completed on YYYY-MM-DD
🔄 ADAPTIVE TASK TRACKING BY LEVEL
Level 1: Quick Bug Fix
Update Frequency: 2-3 updates total
- Initial bug documentation
- Fix implementation
- Verification of fix
Tracking Detail:
- Single task with 1-3 checkboxes
- Focus on problem statement and solution
- Minimal but sufficient documentation
Example Task Entry:
## Current Tasks
- [ ] Fix login button not working
- [ ] Identify root cause
- [ ] Implement fix
- [ ] Verify solution
Example Update Format:
🔄 TASK UPDATE: Fix login button - [X] Complete
- Updated in tasks.md ✓
- Root cause identified: CSS z-index conflict
- Solution implemented and verified
Level 2: Simple Enhancement
Update Frequency: 4-6 updates total
- Initial task creation
- Plan finalization
- Implementation milestones (1-2)
- Testing completion
- Final verification
Tracking Detail:
- Main task with 3-5 subtasks
- Implementation approach documented
- Basic testing steps included
Example Task Entry:
## Current Tasks
- [ ] Add logout button to navbar
- [ ] Create button component
- [ ] Add logout functionality
- [ ] Style button to match design
- [ ] Add tooltip/confirmation
- [ ] Test functionality
Example Update Format:
🔄 TASK UPDATE: Add logout button - In Progress
- Updated in tasks.md ✓
- [X] Create button component
- [X] Add logout functionality
- [ ] Style button to match design
- [ ] Add tooltip/confirmation
- [ ] Test functionality
- Implementation details added to activeContext.md ✓
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.
- 2d ago First seen · 394 lines · 2,597 tokens per session scan A e47ef7487b17
task-tracking is a cursor rule published in the GitHub repository kfnzero/mantis-mcp-server (10 stars, last pushed 12mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,597 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
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.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.