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/neuromechanist/research-skillsWrote 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/neuromechanist/research-skills/dev_workflow)<a href="https://agentmods.dev/rules/neuromechanist/research-skills/dev_workflow"><img src="https://agentmods.dev/badge/rules/neuromechanist/research-skills/dev_workflow.svg" alt="Measured on agentmods" 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.01074 | $0.01074 |
| Opus 5 | $0.00537 | $0.00537 |
| Sonnet 5 | $0.00215 | $0.00215 |
| Haiku 4.5 | $0.00107 | $0.00107 |
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 3d 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 — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
TaskMaster Development Workflow for {{PROJECT_NAME}}
Documentation-Driven Development
Core Documents
- TaskMaster DB: Primary task tracking (.taskmaster/)
- .context/research.md: Solution exploration and technical references
- .context/ideas.md: Abstract concepts and design exploration
- .context/scratch_history.md: Failed approaches and lessons learned
Document Integration
- TaskMaster handles task management
- Use .context/research.md for technical exploration
- Document design decisions in .context/ideas.md
- Track failures in .context/scratch_history.md
Task Management: AI-Powered
Setup
task-master init --yes
task-master parse-prd scripts/prd.txt --num-tasks=15 --research
MCP Tools (Recommended)
get_tasks,next_task,get_task- Task viewingupdate_subtask,update_task- Progress loggingadd_task,expand_task- Task creation/breakdownadd_dependency,validate_dependencies- Dependencies
CLI Fallback
task-master list # View tasks
task-master next # Find next task
task-master show <id> # Task details
task-master set-status <id> --status=in-progress|done
Daily Workflow
- Find next task:
next_task/task-master next - Review context: Check .context/ideas.md and .context/research.md if needed
- Start work: Set status to in-progress
- Research if blocked: Update .context/research.md with findings
- Create branch:
git checkout -b "feature/short-description" - Implement: Code following task requirements
- Log progress:
update_subtask --prompt="implementation notes" - Test & commit: Concise message <50 chars, no emojis
- Mark complete: Set status to done
- Update docs: Document learnings in .context/ files
- Create PR: Descriptive title, reference task in body
Task Breakdown & Dependencies
Complex Tasks
# MCP: expand_task(id="5", num="4", research=true)
task-master expand <id> --num=4 --research
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.
- 3d ago First seen · 148 lines · 1,074 tokens per session scan A f8499b4ec5e5
dev_workflow is a cursor rule published in the GitHub repository neuromechanist/research-skills (45 stars, last pushed 4d ago), licensed BSD-3-Clause. It adds 1,074 tokens to every session, about $0.0054 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-09-04.
Other cursor rules, from other repositories
team-brain
Team Brain sync mode — one start per ticket, then live merge-safe crew memory. Always-on when .team-brain exists or work mentions an initiative/Jira key.
3-process-task-list
Guidelines for managing task lists in markdown files to track progress on completing a PRD.
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
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.
cli-error-handling
CLI command error handling patterns.