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/compozy/gograph/task-developinggit clone --depth 1 https://github.com/compozy/gographWhat 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.00593 | $0.00593 |
| Opus 5 | $0.00296 | $0.00296 |
| Sonnet 5 | $0.00119 | $0.00119 |
| Haiku 4.5 | $0.00059 | $0.00059 |
Grade A, and why
task-developing 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 yesterday.
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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Task List Management
Guidelines for managing task lists in markdown files to track progress on completing a PRD and its technical specification
Task Implementation
<completion_protocol>
- When you finish a sub‑task, immediately mark it as completed by changing
[ ]to[x]. - If all subtasks underneath a parent task are now
[x], also mark the parent task as completed.
- Stop after each sub‑task and wait for the user's go‑ahead. </completion_protocol>
Task List Maintenance
<maintenance_rules>
-
Update the task list as you work:
- Mark tasks and subtasks as completed (
[x]) per the protocol above. - Add new tasks as they emerge.
- Mark tasks and subtasks as completed (
-
Maintain the "Relevant Files" section:
- List every file created or modified.
- Give each file a one‑line description of its purpose. </maintenance_rules>
AI Instructions
<ai_workflow> When working with task lists, the AI must:
- Regularly update the task list file after finishing any significant work.
- Follow the completion protocol:
- Mark each finished sub‑task
[x]. - Mark the parent task
[x]once all its subtasks are[x].
- Mark each finished sub‑task
- Add newly discovered tasks.
- Keep "Relevant Files" accurate and up to date.
- Before starting work, check which sub‑task is next.
- After implementing a sub‑task, update the file and then pause for user approval.
- ALWAYS use the task.mdc file as the primary reference for implementation
- NEVER skip test assertions defined in the task requirements </ai_workflow>
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.
- yesterday First seen · 62 lines · 593 tokens per session scan A 54a38a98d4a2
task-developing is a cursor rule published in the GitHub repository compozy/gograph (9 stars, last pushed 1y ago), licensed MIT. It adds 593 tokens to every session, about $0.0030 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-31.
Other cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.