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/dev_workflow)<a href="https://agentmods.dev/rules/learnwithcc/tally-mcp/dev_workflow"><img src="https://agentmods.dev/badge/rules/learnwithcc/tally-mcp/dev_workflow/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/dev_workflow"><img src="https://agentmods.dev/badge/rules/learnwithcc/tally-mcp/dev_workflow.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.04302 | $0.04302 |
| Opus 5.5 | $0.01721 | $0.01721 |
| Sonnet 5.5 | $0.00860 | $0.00860 |
| Haiku 4.5 | $0.00430 | $0.00430 |
Grade A, and why
dev_workflow 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.
This is a copy
100% identical to dev_workflow — 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.
How it starts
The opening of the file, as written. The whole thing — 239 lines — stays where its author put it; the contents beside it link to each section on GitHub.
description: Guide for using Task Master to manage task-driven development workflows globs: */ alwaysApply: true
Task Master Development Workflow
This guide outlines the typical process for using Task Master to manage software development projects.
Primary Interaction: MCP Server vs. CLI
Task Master offers two primary ways to interact:
-
MCP Server (Recommended for Integrated Tools):
- For AI agents and integrated development environments (like Cursor), interacting via the MCP server is the preferred method.
- The MCP server exposes Task Master functionality through a set of tools (e.g.,
get_tasks,add_subtask). - This method offers better performance, structured data exchange, and richer error handling compared to CLI parsing.
- Refer to
mcp.mdcfor details on the MCP architecture and available tools. - A comprehensive list and description of MCP tools and their corresponding CLI commands can be found in
taskmaster.mdc. - Restart the MCP server if core logic in
scripts/modulesor MCP tool/direct function definitions change.
-
task-masterCLI (For Users & Fallback):- The global
task-mastercommand provides a user-friendly interface for direct terminal interaction. - It can also serve as a fallback if the MCP server is inaccessible or a specific function isn't exposed via MCP.
- Install globally with
npm install -g task-master-aior use locally vianpx task-master-ai .... - The CLI commands often mirror the MCP tools (e.g.,
task-master listcorresponds toget_tasks). - Refer to
taskmaster.mdcfor a detailed command reference.
- The global
Standard Development Workflow Process
- Start new projects by running
initialize_projecttool /task-master initorparse_prd/task-master parse-prd --input='<prd-file.txt>'(seetaskmaster.mdc) to generate initial tasks.json - Begin coding sessions with
get_tasks/task-master list(seetaskmaster.mdc) to see current tasks, status, and IDs - Determine the next task to work on using
next_task/task-master next(seetaskmaster.mdc). - Analyze task complexity with
analyze_project_complexity/task-master analyze-complexity --research(seetaskmaster.mdc) before breaking down tasks - Review complexity report using
complexity_report/task-master complexity-report(seetaskmaster.mdc). - Select tasks based on dependencies (all marked 'done'), priority level, and ID order
- Clarify tasks by checking task files in tasks/ directory or asking for user input
- View specific task details using
get_task/task-master show <id>(seetaskmaster.mdc) to understand implementation requirements - Break down complex tasks using
expand_task/task-master expand --id=<id> --force --research(seetaskmaster.mdc) with appropriate flags like--force(to replace existing subtasks) and--research. - Clear existing subtasks if needed using
clear_subtasks/task-master clear-subtasks --id=<id>(seetaskmaster.mdc) before regenerating - Implement code following task details, dependencies, and project standards
- Verify tasks according to test strategies before marking as complete (See
tests.mdc) - Mark completed tasks with
set_task_status/task-master set-status --id=<id> --status=done(seetaskmaster.mdc) - Update dependent tasks when implementation differs from original plan using
update/task-master update --from=<id> --prompt="..."orupdate_task/task-master update-task --id=<id> --prompt="..."(seetaskmaster.mdc) - Add new tasks discovered during implementation using
add_task/task-master add-task --prompt="..." --research(seetaskmaster.mdc). - Add new subtasks as needed using
add_subtask/task-master add-subtask --parent=<id> --title="..."(seetaskmaster.mdc). - Append notes or details to subtasks using
update_subtask/task-master update-subtask --id=<subtaskId> --prompt='Add implementation notes here...\nMore details...'(seetaskmaster.mdc). - Generate task files with
generate/task-master generate(seetaskmaster.mdc) after updating tasks.json - Maintain valid dependency structure with
add_dependency/remove_dependencytools ortask-master add-dependency/remove-dependencycommands,validate_dependencies/task-master validate-dependencies, andfix_dependencies/task-master fix-dependencies(seetaskmaster.mdc) when needed - Respect dependency chains and task priorities when selecting work
- Report progress regularly using
get_tasks/task-master list - Reorganize tasks as needed using
move_task/task-master move --from=<id> --to=<id>(seetaskmaster.mdc) to change task hierarchy or ordering
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 · 239 lines · 4,302 tokens per session scan A de4c7e05df36
dev_workflow is a cursor rule published in the GitHub repository learnwithcc/tally-mcp (8 stars, last pushed 1y ago), licensed ISC. It adds 4,302 tokens to every session, about $0.0172 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to dev_workflow, differing in 0 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.