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/learnwithcc/tally-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/learnwithcc/tally-mcp/taskmaster)<a href="https://agentmods.dev/rules/learnwithcc/tally-mcp/taskmaster"><img src="https://agentmods.dev/badge/rules/learnwithcc/tally-mcp/taskmaster/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/learnwithcc/tally-mcp/taskmaster"><img src="https://agentmods.dev/badge/rules/learnwithcc/tally-mcp/taskmaster.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.08043 | $0.08043 |
| Opus 5.5 | $0.03217 | $0.03217 |
| Sonnet 5.5 | $0.01609 | $0.01609 |
| Haiku 4.5 | $0.00804 | $0.00804 |
Grade B, and why
taskmaster scanned grade B with 1 finding 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.
Reads MCP configurationmediumAgent snooping
mcp.json carries server URLs and auth tokens; reading it lets a mod discover and abuse other integrations.
**Set API keys** in your **`.env`** file in the project root (for CLI use) or within the `env` section of your **`.cursor/mcp.json`** file (for MCP/Cursor integration). All other settings (model choice, max tokens, tempe This is a copy
88% identical to taskmaster — 182 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.
How it starts
The opening of the file, as written. The whole thing — 408 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Taskmaster Tool & Command Reference
This document provides a detailed reference for interacting with Taskmaster, covering both the recommended MCP tools, suitable for integrations like Cursor, and the corresponding task-master CLI commands, designed for direct user interaction or fallback.
Note: For interacting with Taskmaster programmatically or via integrated tools, using the MCP tools is strongly recommended due to better performance, structured data, and error handling. The CLI commands serve as a user-friendly alternative and fallback.
Important: Several MCP tools involve AI processing... The AI-powered tools include parse_prd, analyze_project_complexity, update_subtask, update_task, update, expand_all, expand_task, and add_task.
Initialization & Setup
1. Initialize Project (init)
- MCP Tool:
initialize_project - CLI Command:
task-master init [options] - Description:
Set up the basic Taskmaster file structure and configuration in the current directory for a new project. - Key CLI Options:
--name <name>:Set the name for your project in Taskmaster's configuration.--description <text>:Provide a brief description for your project.--version <version>:Set the initial version for your project, e.g., '0.1.0'.-y, --yes:Initialize Taskmaster quickly using default settings without interactive prompts.
- Usage: Run this once at the beginning of a new project.
- MCP Variant Description:
Set up the basic Taskmaster file structure and configuration in the current directory for a new project by running the 'task-master init' command. - Key MCP Parameters/Options:
projectName:Set the name for your project.(CLI:--name <name>)projectDescription:Provide a brief description for your project.(CLI:--description <text>)projectVersion:Set the initial version for your project, e.g., '0.1.0'.(CLI:--version <version>)authorName:Author name.(CLI:--author <author>)skipInstall:Skip installing dependencies. Default is false.(CLI:--skip-install)addAliases:Add shell aliases tm and taskmaster. Default is false.(CLI:--aliases)yes:Skip prompts and use defaults/provided arguments. Default is false.(CLI:-y, --yes)
- Usage: Run this once at the beginning of a new project, typically via an integrated tool like Cursor. Operates on the current working directory of the MCP server.
- Important: Once complete, you MUST parse a prd in order to generate tasks. There will be no tasks files until then. The next step after initializing should be to create a PRD using the example PRD in .taskmaster/templates/example_prd.txt.
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 · 408 lines · 8,043 tokens per session scan B 94b4a92ce28e
taskmaster is a cursor rule published in the GitHub repository learnwithcc/tally-mcp (8 stars, last pushed 1y ago), licensed ISC. It adds 8,043 tokens to every session, about $0.0322 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads mcp configuration). It is 88% identical to taskmaster, differing in 182 lines, and is treated as a copy.
Other cursor rules, from other repositories
planning
Complete feature development lifecycle using memory-backed planning. Creates requirements, design, and task memories. Use when: starting new features, planning implementations, organizing development work, managing project specifications.
development-workflow
Defines the standard development workflow, including the mandatory file analysis protocol, smart development patterns, and the prioritization of specialized MCP tools to ensure code quality, consistency, and efficiency.
tools-reference
Complete reference for all MCP tools: CLI operations, API validation, documentation lookup, GitHub integration, file analysis, code investigation, memory management, task management. Use when: planning features, developing code, researching solutions, managing project knowledge, analyzing files, debugging issues.
feature-lifecycle
Defines the complete feature development lifecycle, from initial research and requirement gathering to design, planning, and task creation. This rule integrates documentation research, community feedback via GitHub, and memory-backed planning into a cohesive workflow.
dev_workflow
Cursor rule "dev_workflow" from itsbrex/attio-mcp-server, covering task master development workflow, primary interaction: mcp server vs. cli, standard development workflow process, task complexity analysis and task breakdown process.
taskmaster
Cursor rule "taskmaster" from itsbrex/attio-mcp-server, covering taskmaster tool & command reference, initialization & setup, 1. initialize project (init), 2. parse prd (parseprd) and ai model configuration.