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/Activ8-AI/Teamwork-MCPWrote 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/activ8-ai/teamwork-mcp/instructions-for-todo-list)<a href="https://agentmods.dev/rules/activ8-ai/teamwork-mcp/instructions-for-todo-list"><img src="https://agentmods.dev/badge/rules/activ8-ai/teamwork-mcp/instructions-for-todo-list.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.00000 | $0.00368 |
| Opus 5 | $0.00000 | $0.00184 |
| Sonnet 5 | $0.00000 | $0.00074 |
| Haiku 4.5 | $0.00000 | $0.00037 |
Grade A, and why
instructions-for-todo-list 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 instructions-for-todo-list — 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
description: globs: todo.md alwaysApply: true
Task Management with TODO.md
If a TODO.md file exists in the root of a solution, it outlines the current tasks. Team members can refer to this file to identify tasks they can assist with, especially after completing previous assignments.
Tasks are prioritized as follows:
🟥 High Priority: Known issues that are currently broken and require immediate attention. 🟨 Medium Priority: New tasks that need to be addressed. ✅ Completed Tasks: Tasks that have been finished successfully.
When contributing to a task:
- If you verify that your changes have completed the task, update its status in the TODO.md file, verification must be in the form of running a test to prove that then functionality works, or by user confirmation.
- If it requires manual verification by the user, notify them. Once confirmed, update the task status accordingly.
- All tasks should be in bullet lists
- When adding new tasks, use the 🟨 emoji. Upon completion, mark tasks with a ✅. For known issues, denote them with a 🟥.
Group competed tasks under third level headings for each date that issues were fixed in the following format: MM/DD/YYYY
New date completed task sections should be added above all other dated sections.
Always add completed tasks to the top of the current date's list so we see the most recent completed items first, the date sections should also show the most recent date at the top to make it quicker to see the most recently changes.
Markdown Formatting Standards
Always include a blank line above and below every heading in markdown files, such as TODO.md, to maintain readability and consistency. Always ensure there is a blank line at the end of any markdown file.
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 · 35 lines · 0 tokens per session scan A f310bd233092
instructions-for-todo-list is a cursor rule published in the GitHub repository Activ8-AI/Teamwork-MCP (0 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 368 tokens. A static security scan graded it A with 0 findings. It is 100% identical to instructions-for-todo-list, 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).