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/matipojo/cursor-rulesWrote 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/matipojo/cursor-rules/parse-and-run-tasks)<a href="https://agentmods.dev/rules/matipojo/cursor-rules/parse-and-run-tasks"><img src="https://agentmods.dev/badge/rules/matipojo/cursor-rules/parse-and-run-tasks/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/matipojo/cursor-rules/parse-and-run-tasks"><img src="https://agentmods.dev/badge/rules/matipojo/cursor-rules/parse-and-run-tasks.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.00000 | $0.00361 |
| Opus 5.5 | $0.00000 | $0.00144 |
| Sonnet 5.5 | $0.00000 | $0.00072 |
| Haiku 4.5 | $0.00000 | $0.00036 |
Grade A, and why
parse-and-run-tasks 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.
What it actually says
Parsing PRD and Implementation into Tasks
This guide outlines the process of parsing a Product Requirements Document (PRD) and its implementation into actionable tasks, and tracking overall progress.
Steps
-
Review the PRD: Carefully read the PRD to understand the feature requirements, user stories, and acceptance criteria.
-
Break Down the PRD: Divide the PRD into logical sections or user stories. Each section should represent a distinct feature or functionality.
-
Create Tasks: For each section, create a list of tasks. Each task should be specific, actionable, and have a clear outcome. Use a consistent format, such as:
- Task ID
- Task Name
- Description
- File(s) to modify
- Status (e.g., pending, in_progress, completed)
-
Prioritize Tasks: Arrange tasks in a logical order, considering dependencies and critical paths.
-
Track Progress: Use a task tracking file (e.g.,
tasks.json) to monitor the status of each task. Update the status as you progress through the implementation. -
Iterate: Iterate the task list and run without user needs to confirm
Example Task Structure
{
"feature_name": {
"tasks": [
{
"id": "task_id",
"name": "Task Name",
"description": "Detailed description of the task",
"file": "path/to/file",
"status": "pending"
}
],
"current_task": null,
"last_updated": "YYYY-MM-DDTHH:MM:SSZ"
}
}
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 · 47 lines · 0 tokens per session scan A 2c60aa4c7e15
parse-and-run-tasks is a cursor rule published in the GitHub repository matipojo/cursor-rules (31 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 361 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.
Other cursor rules, from other repositories
slice-tasks
PLANNING SPINE STEP 2 of 3 — Slice the work: break a scoped PRD into vertical-slice stories in specs/epics/. Use after scope-work (step 1), before plan-work (step 3). Not a substitute for scope-work or plan-work.
iris
GitHub operations specialist — branches, pull requests, issues, releases, tags. Called by zeus after review. Never pushes or merges without explicit human approval. Integrates with VS Code GitHub Pull Requests extension.
elite-orchestrator
Elite orchestrator for mission-critical, enterprise-scale tasks requiring strategic coordination of 7+ agents across all domains. Makes architectural decisions, manages risk, ensures business continuity, and delivers enterprise-grade outcomes. Use for platform migrations, security incidents, multi-system integrations…
project-onboarding-rule
Automatically onboards existing projects into the AI-driven development workflow.
linear-in-review
After finishing a Linear issue, set its status to In Review (never Done).
sprint-planning
BMAD BMM Agent: sprint-planning.