agentmods.dev

planr-pipeline: Instructions file for Claude Code

CLAUDE.md

planr-pipeline CLAUDE.md is an instructions file for Claude Code from openplanr/planr-pipeline. It costs 2,772 tokens per session, scanned A, a copy of OpenPlanr AGENTS.md, MIT.

Instructions for using OpenPlanr, an agile planning system whose project files live in a .planr directory. They require developers to read the task, its parent user story, its feature, and related architecture information before coding.

In plain words
What is it for?
Use them when working on tasks in a planr-pipeline project, especially when selecting an unfinished subtask and tracing it through its user story, feature, and technical context.
Why use it?
They prevent implementation work from missing requirements, dependencies, or decisions recorded higher in the planning hierarchy. This gives each task the context needed to implement it correctly.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md. Also seen: mentions Claude Code.

This is openplanr/planr-pipeline's own configuration. It tells Claude Code how to work on planr-pipeline itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything planr-pipeline configures →

not rated 2repo 1mo ago A scan 2,772 tokens copy · 88% MIT
View source ↗ openplanr/planr-pipeline
Reuse

Borrowing it

Nothing to install: this file belongs to openplanr/planr-pipeline. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/openplanr/planr-pipeline/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/openplanr/planr-pipeline

Made for: Claude Code.

Wrote 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.

agentmods badge for planr-pipeline CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/openplanr/planr-pipeline/claude-md/github.svg)](https://agentmods.dev/instructions/openplanr/planr-pipeline/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/openplanr/planr-pipeline/claude-md"><img src="https://agentmods.dev/badge/instructions/openplanr/planr-pipeline/claude-md/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.

agentmods 80×15 button for planr-pipeline CLAUDE.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/openplanr/planr-pipeline/claude-md"><img src="https://agentmods.dev/badge/instructions/openplanr/planr-pipeline/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 2,772 This file is loaded in full into every session.
When invoked 2,772 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 88% copy Near-identical to another mod in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.02772 $0.02772
Opus 5 $0.01386 $0.01386
Sonnet 5 $0.00554 $0.00554
Haiku 4.5 $0.00277 $0.00277

Measured 8d ago against content hash ae627912f4c9, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

planr-pipeline CLAUDE.md 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 8d 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.

Origin

This is a copy

88% identical to OpenPlanr AGENTS.md — 70 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

CLAUDE.md · 244 lines

How it starts

The opening of the file, as written. The whole thing — 244 lines — stays where its author put it; the contents beside it link to each section on GitHub.

planr-pipeline — Agile Planning & Implementation Guide

Generated by OpenPlanr on 2026-05-03

This project uses OpenPlanr for agile planning. All artifacts are in .planr/.

Context-Gathering Protocol

Before implementing ANY task or subtask, you MUST gather full planning context by reading the artifact hierarchy. Follow this exact sequence:

Step 1: Read the Task List

  • Open the task file from .planr/tasks/ (e.g., TASK-001-*.md) or quick task from .planr/quick/
  • Parse the frontmatter to find storyId or featureId
  • 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:

  1. 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 featureId from frontmatter

  2. Feature → .planr/features/FEAT-XXX-*.md

    • Read the full feature (overview, functional requirements, technical considerations)
    • Extract the parent epicId from frontmatter

  3. 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.md for current progress

Step 4: Scan the Codebase

Before writing code, understand what exists:

  1. Identify the tech stack — Read package.json, tsconfig.json, or equivalent
  2. Scan the source tree — List directories under src/ (or project root)
  3. Read architecture files — Look for these high-priority files:
    • Type definitions: src/models/types.ts, src/types/index.ts, or src/types.ts
    • Core services: src/services/ — understand CRUD patterns
    • Entry point: src/index.ts, src/main.ts, or src/app.ts — understand registration patterns
    • Config: src/config.ts or src/services/config-service.ts
  4. Find related files — Search for files matching keywords from the task description
  5. Check project rules — Read .planr/rules.md if it exists (MANDATORY rules)

Read the full file on GitHub · 244 lines

Changes

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.

  1. 8d ago First seen · 244 lines · 2,772 tokens per session scan A ae627912f4c9

Subscribe to this mod's changes

planr-pipeline CLAUDE.md is an instructions file published in the GitHub repository openplanr/planr-pipeline (2 stars, last pushed 1mo ago), licensed MIT. It adds 2,772 tokens to every session, about $0.0139 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to OpenPlanr AGENTS.md, differing in 70 lines, and is treated as a copy.

Claude CodeCode GenerationPlanningai-agentsclaude-code-pluginspec-drivensubagents
Related

Other instructions, from other repositories

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,153 tokens

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 6,785 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,469 tokens

deepseek-harness AGENTS.md

AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.

deepseek-ai/deepseek-harness · 3,737 tokens