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/openplanr/planr-pipelineWrote 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/openplanr/planr-pipeline/implement-task-list)<a href="https://agentmods.dev/rules/openplanr/planr-pipeline/implement-task-list"><img src="https://agentmods.dev/badge/rules/openplanr/planr-pipeline/implement-task-list/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/openplanr/planr-pipeline/implement-task-list"><img src="https://agentmods.dev/badge/rules/openplanr/planr-pipeline/implement-task-list.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.00014 | $0.01001 |
| Opus 5.5 | $0.00006 | $0.00400 |
| Sonnet 5.5 | $0.00003 | $0.00200 |
| Haiku 4.5 | $0.00001 | $0.00100 |
Grade A, and why
implement-task-list 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.
How it starts
The opening of the file, as written. The whole thing — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implement Task List
You are an implementation assistant for planr-pipeline. Before writing any code, you MUST gather full planning context by reading the artifact hierarchy.
Context-Gathering Protocol
Before implementing ANY subtask, follow this exact sequence:
Step 1: Read the Task List
- Open the task file from
.planr/tasks/(e.g.,TASK-001-*.md) - Parse the frontmatter to find
storyIdorfeatureId - Identify the target subtask (first unchecked
- [ ]item) - Read ALL subtasks to understand the full scope and dependencies
Step 2: Read the Parent Chain (MANDATORY)
Follow the artifact hierarchy upward — each level adds critical context:
-
User Story →
.planr/stories/US-XXX-*.md- Read the full story (role, goal, benefit, acceptance criteria)
- Find and read the matching Gherkin file:
.planr/stories/US-XXX-gherkin.feature - Extract the parent
featureIdfrom frontmatter
-
Feature →
.planr/features/FEAT-XXX-*.md- Read the full feature (overview, functional requirements, technical considerations)
- Extract the parent
epicIdfrom frontmatter
-
Epic →
.planr/epics/EPIC-XXX-*.md- Read the epic summary (business value, problem statement, success criteria)
- This provides the WHY behind the work
Step 3: Read Architecture Context
- Read ALL ADRs in
.planr/adrs/— these are binding technical decisions - Check
.planr/checklists/AGILE-DEVELOPMENT-GUIDE.mdfor current progress
Step 4: Scan the Codebase
Before writing code, understand what exists:
- Identify the tech stack — Read
package.json,tsconfig.json, or equivalent - Scan the source tree — List directories under
src/(or project root) - Read architecture files — Look for these high-priority files:
- Type definitions:
src/models/types.ts,src/types/index.ts, orsrc/types.ts - Core services:
src/services/— understand CRUD patterns - Entry point:
src/index.ts,src/main.ts, orsrc/app.ts— understand registration patterns - Config:
src/config.tsorsrc/services/config-service.ts
- Type definitions:
- Find related files — Search for files matching keywords from the task description
- Check project rules — Read
.planr/rules.mdif it exists (MANDATORY rules)
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 · 92 lines · 14 tokens per session scan A 8c69e0a56224
implement-task-list is a cursor rule published in the GitHub repository openplanr/planr-pipeline (2 stars, last pushed 21d ago), licensed MIT. It adds 14 tokens to every session and 1,001 once invoked, about $0.0001 per session on Opus 5.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
mstar-cursor-plan-mode
When using Cursor Plan mode with Morning Star, dual-write CreatePlan to .mstar/ harness artifacts and require per-task commits.
mstar-entry
Ensure Morning Star core skill is loaded first in Cursor plugin usage.
archcore-context
Archcore knowledge base context — document types, MCP tools, and conventions for working with .archcore/ documents.
archcore-files
Enforce MCP-only operations when working with .archcore/ files.
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.