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.
curl -O https://raw.githubusercontent.com/openplanr/planr-pipeline/main/AGENTS.mdgit 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/instructions/openplanr/planr-pipeline/agents-md)<a href="https://agentmods.dev/instructions/openplanr/planr-pipeline/agents-md"><img src="https://agentmods.dev/badge/instructions/openplanr/planr-pipeline/agents-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.
<a href="https://agentmods.dev/instructions/openplanr/planr-pipeline/agents-md"><img src="https://agentmods.dev/badge/instructions/openplanr/planr-pipeline/agents-md.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.03010 | $0.03010 |
| Opus 5.5 | $0.01204 | $0.01204 |
| Sonnet 5.5 | $0.00602 | $0.00602 |
| Haiku 4.5 | $0.00301 | $0.00301 |
Grade A, and why
planr-pipeline AGENTS.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 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- planr-pipeline CLAUDE.md — 86% identical, 131 lines differ
How it starts
The opening of the file, as written. The whole thing — 273 lines — stays where its author put it; the contents beside it link to each section on GitHub.
planr-pipeline — Agent Instructions
Generated by OpenPlanr on 2026-05-03
This project follows a structured agile workflow. All planning artifacts are in .planr/.
Context-Gathering Protocol
Before implementing a task, gather the strongest available planning context. Use
the artifact hierarchy when it exists; when it does not, use the explicit user
request, repository ADRs/docs, and the existing code as the authoritative context.
Missing .planr/ artifacts must never block an otherwise well-specified change.
Step 1: Read the Task List
- If
.planr/tasks/or.planr/quick/exists, open the relevant task file - Parse the frontmatter to find
storyIdorfeatureId - Identify the target subtask (first unchecked
- [ ]item) - Read ALL subtasks to understand the full scope and dependencies
- If no task artifact exists, treat the user's explicit implementation plan as the task specification and continue to Step 3.
Step 2: Read the Parent Chain (when present)
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 · 273 lines · 3,010 tokens per session scan A d81ce2ba439d
planr-pipeline AGENTS.md is an instructions file published in the GitHub repository openplanr/planr-pipeline (2 stars, last pushed 27d ago), licensed MIT. It adds 3,010 tokens to every session, about $0.0120 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 instructions, from other repositories
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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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.
vscode copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deno copilot-instructions.md
Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.