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/aiurda/devcontext/020-tasks-workflowgit clone --depth 1 https://github.com/aiurda/devcontextWhat 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.02230 | $0.02230 |
| Opus 5 | $0.01115 | $0.01115 |
| Sonnet 5 | $0.00446 | $0.00446 |
| Haiku 4.5 | $0.00223 | $0.00223 |
Grade A, and why
020-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 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.
How it starts
The opening of the file, as written. The whole thing — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Task Workflow System (Multi-File in tasks/ Directory)
- Purpose: Standardize task implementation with proper tracking and status updates across a distributed task list.
- Implementation: Tasks are distributed across
tasks/tasks-N.mdfiles, indexed bytasks/tasks-index.md.
Overall Task Management Structure
-
Index File (
tasks/tasks-index.md):-
Contains the Overall Project Task Summary (Total Tasks, Pending, Complete for the entire project).
-
Contains the Task File Index, mapping Task ID ranges to specific
tasks/tasks-N.mdfiles.## Overall Project Task Summary - **Total Tasks**: {Total for project} - **Pending**: {Pending for project} - **Complete**: {Complete for project} ## Task File Index - `tasks/tasks-1.md`: Contains Tasks {start_id_1} - {end_id_1} ({task_count_1} tasks) - `tasks/tasks-2.md`: Contains Tasks {start_id_2} - {end_id_2} ({task_count_2} tasks) - ...
-
-
Task Files (
tasks/tasks-N.md):-
Each file starts with its own local summary:
## Summary (tasks-N.md) // Clarify which task file this summary is for - **Tasks in this file**: {Count for this file} - **Task IDs**: {start_id_N} - {end_id_N} // e.g., 001 - 030 -
Followed by the
## Taskssection containing individual tasks.
-
-
Task Structure (within
tasks/tasks-N.md)-
Tasks are defined with:
### Task ID: {ID} - **Title**: Example title - **File**: example/file/path (relative to project root, excluding project root dir) - **Complete**: [ ] #### Prompt: ```markdown DETAILED PROMPT INCLUDING TARGET FILE PATH AND CONTEXT ```
-
Task Management Workflow
1. Locating a Task
- When user requests "next task":
- Open and consult
tasks/tasks-index.mdto understand the overall project status and identify the sequence of task files. - Iterate through
tasks/tasks-1.md,tasks/tasks-2.md, etc., in numerical order as listed in the index. - Within each
tasks/tasks-N.mdfile, find the first task whereComplete: [ ]. This is the next task. - Note the
tasks/tasks-N.mdfile this task resides in.
- Open and consult
- When user specifies a Task ID (e.g., "Task 042"):
- Open and consult
tasks/tasks-index.md. - Read the "Task File Index" to determine which
tasks/tasks-N.mdfile contains that Task ID. - Open the identified
tasks/tasks-N.mdfile (e.g., if Task 042 is intasks-2.md, opentasks/tasks-2.md). - Locate the task with the specified
### Task ID: {ID}.
- Open and consult
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 · 186 lines · 2,230 tokens per session scan A 1b8ba1a4d25d
020-tasks-workflow is a cursor rule published in the GitHub repository aiurda/devcontext (47 stars, last pushed 1y ago), licensed MIT. It adds 2,230 tokens to every session, about $0.0112 per session on Opus 5. 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.
Other cursor rules, from other repositories
100-memory-system
Comprehensive Memory System architecture for autonomous Cursor operation.
cursorrules
The FIRST action in the BEGINNING of EVERY response MUST be to initialize the conversation with this single tool call and display the banner from the response immediately after. It MUST be called EXACTLY ONCE per conversation and ONLY at the very beginning after receiving user input.
200-tasks-workflow
Task Workflow System for project implementation.
010-cursor-rules
Guidelines for creating and maintaining Cursor rules to ensure consistency and effectiveness.
cursorrules
Cursor rule "cursorrules" from 0xNyk/awesome-agent-cortex, covering .cursorrules — cursor ide rules file, project context, tech stack, code style and development workflow.
security
Security rules for all source files.