cursor_conductor_tasks_workflow

cursor_conductor_tasks_workflow is a cursor rule for coding agents from hridaya423/conductor-tasks. It costs 0 tokens per session (3,751 once invoked), scanned A, original, MIT.

A set of rules for managing software work with Conductor Tasks, using structured tools or a command-line program. It guides an AI assistant through planning, breaking down, and updating development tasks.

In plain words
What is it for?
Use it to review task complexity, split work into smaller steps, follow a standard development workflow, and update tasks or add notes through Conductor Tasks.
Why use it?
It gives AI-driven development a consistent process, so tasks are less likely to be handled in an unclear or inconsistent order.

Cursor rule

Install

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.

agentmods
npx agentmods add rules/hridaya423/conductor-tasks/cursor_conductor_tasks_workflow
Clone the repo
git clone --depth 1 https://github.com/hridaya423/conductor-tasks

Wrote 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.

agentmods badge for cursor_conductor_tasks_workflow

README.md
[![agentmods](https://agentmods.dev/badge/rules/hridaya423/conductor-tasks/cursor_conductor_tasks_workflow.svg)](https://agentmods.dev/rules/hridaya423/conductor-tasks/cursor_conductor_tasks_workflow)
Your own site
<a href="https://agentmods.dev/rules/hridaya423/conductor-tasks/cursor_conductor_tasks_workflow"><img src="https://agentmods.dev/badge/rules/hridaya423/conductor-tasks/cursor_conductor_tasks_workflow.svg" alt="Measured on agentmods" height="20"></a>
Per session 0 Nothing until a file matches its globs; then the whole rule loads.
When invoked 3,751 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.03751
Opus 5 $0.00000 $0.01876
Sonnet 5 $0.00000 $0.00750
Haiku 4.5 $0.00000 $0.00375

Measured 4d ago against content hash 1f0533f4cc9d, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

cursor_conductor_tasks_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 4d 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.

src/ide/rule_templates/cursor_conductor_tasks_workflow.mdc · 192 lines

How it starts

The opening of the file, as written. The whole thing — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.


description: Comprehensive guide for using Conductor Tasks to manage AI-driven development workflows, closely following best practices. globs: */ alwaysApply: true

Conductor Tasks: Comprehensive AI Development Workflow

This guide outlines the detailed process for using Conductor Tasks to manage software development projects, especially when an AI assistant is driving the workflow via MCP tools. It is based on established best practices for AI task management.

Primary Interaction: MCP Server vs. CLI

Conductor Tasks offers two primary ways to interact:

  1. MCP Server (Strongly Recommended for AI Integration):

    • For AI agents and integrated development environments (like Cursor), interacting via the MCP server is the mandated method.
    • The MCP server exposes Conductor Tasks functionality through a set of structured tools (e.g., `get-task`, `update-task`, `list-tasks`, `add-task-note`).
    • This method offers better performance, structured data exchange (JSON), richer error handling, and more consistent behavior.
    • Always prioritize using MCP tools when available and as described.
  2. `conductor-tasks` CLI (For Users & Manual Operations):

    • The global `conductor-tasks` command provides a user-friendly interface for direct terminal interaction by developers.
    • CLI commands often mirror MCP tools (e.g., `conductor-tasks list` corresponds to the `list-tasks` MCP tool).
    • As an AI, you should not attempt to use or parse CLI output. Your interaction is exclusively through MCP tools.

Standard Development Workflow Process (AI-Driven)

The following steps detail a typical AI-assisted development workflow using Conductor Tasks MCP tools. Adherence to this process, especially the note-taking, is crucial.

  1. Project Initialization:
    • If starting a new project or if `TASKS.md` (the central task definition file) is missing, use the `initialize-project` tool. This creates `TASKS.md` and any necessary project structure (e.g., `.conductor/` directory) and IDE rules.
    • If a Product Requirements Document (PRD) is provided, use `parse-prd --input='<path_to_prd_file>'` (if available as an MCP tool) or guide the user to run the equivalent CLI command to populate `TASKS.md` with initial tasks.

Read the full file on GitHub · 192 lines

Changes

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.

  1. 4d ago First seen · 192 lines · 0 tokens per session scan A 1f0533f4cc9d

Subscribe to this mod's changes

cursor_conductor_tasks_workflow is a cursor rule published in the GitHub repository hridaya423/conductor-tasks (74 stars, last pushed 7mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,751 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-30.