planr: Instructions file for Codex

AGENTS.md

planr AGENTS.md is an instructions file for Codex, OpenCode from instructa/planr. It costs 734 tokens per session, scanned A, original, MIT.

Repository instructions for working on instructa/planr, a local-first planning and execution tool for coding agents. They define the product documents, architecture boundaries, data contracts, and expected workflow.

In plain words
What is it for?
Use them when implementing or documenting Planr features, consulting product and technical plans, following frozen contracts, and preserving map, evidence, approval, and closure rules.
Why use it?
They give agents a consistent source of truth for how Planr should be designed, changed, logged, reviewed, and completed.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md.

This is instructa/planr's own configuration. It tells Codex and OpenCode how to work on planr 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 configures →

Reuse

Borrowing it

Nothing to install: this file belongs to instructa/planr. 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/instructa/planr/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/instructa/planr

Made for: Codex, OpenCode.

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 AGENTS.md

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

agentmods 80×15 button for planr AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/instructa/planr/agents-md"><img src="https://agentmods.dev/badge/instructions/instructa/planr/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 734 This file is loaded in full into every session.
When invoked 734 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 original No closer match found 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.00734 $0.00734
Opus 5.5 $0.00294 $0.00294
Sonnet 5.5 $0.00147 $0.00147
Haiku 4.5 $0.00073 $0.00073

Measured 1mo ago against content hash 7604177f4e38, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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

AGENTS.md · 37 lines

How it starts

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

Agent guidance for planr

planr is a small planning layer for agent-built products: tasks as a Markdown graph in a planning repository, a dependency-free Node CLI, a board (standalone HTML and bb plugin) and one Agent Skill. Building happens elsewhere (for example split-orchestrator). planr says what is next; it never builds, reviews or verifies.

Read docs/contract.md (data and CLI contract) before changing code, and bb-plugin/README.md before changing the plugin.

Hard limits (crossing these needs a maintainer's explicit OK)

  • No database, no locks/leases/heartbeats/atomic pick, no daemon, no MCP or HTTP server. Exception: planr board --serve, a loopback-only file server with live reload.
  • No per-task gates, evidence system, auto-created fix/review items, or custom benchmark harness.
  • No new task statuses. Statuses: open, in-progress, review, blocked, decision, done, dropped.
  • Node ≥ 20, no runtime dependencies, no network access.

Stop and ask a maintainer when a change would cross one of these limits, introduces a new persistence mechanism, or makes a dispatcher do more than start threads.

Size orientation (not a gate)

Rough sizes: engine (skills/planr/scripts/) around 800 lines, skill around 60, tests around 150 (graph rules and frontmatter rewriting only, no regression test per bug fix). Format honestly: one statement per line, ≤ 110 characters, never compress code to hit a number. Going over is fine; mention the numbers in the handoff and do not stop work or ask about it.

Conventions

  • One owner per rule: readiness, unlocks and validation live only in skills/planr/scripts/lib/graph.mjs; the board reads derived fields and never recomputes them.
  • The planning repository is the source of truth. The engine and CLI never write outside it and never commit, push, merge or deploy. Exception: the bb plugin's host entry commits and pushes human board actions (approve goal, close goal, task checked) from its own worktree, as described in bb-plugin/README.md.
  • bb plugin (bb-plugin/): live tests only against an isolated local bb instance, never a bb server used for real work. Installing a development build there needs a maintainer's OK.
  • Tests run with node --test. Exercise real planning data only in a throwaway clone, never in a live planning repo. Fixtures stay synthetic.
  • Keep artifacts/ untracked; it holds local agent run records.
  • Internal plans, decisions and release notes stay outside this repository.
  • English for code, docs and UI labels. Task titles keep the planning repo's language.

Read the full file on GitHub · 37 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. 1mo ago Changed · +14 lines · +439 tokens per session 7604177f4e38
  2. 2mo ago First seen · 23 lines · 295 tokens per session scan A 3938baafc6d0

Subscribe to this mod's changes

planr AGENTS.md is an instructions file published in the GitHub repository instructa/planr (74 stars, last pushed 17d ago), licensed MIT. It adds 734 tokens to every session, about $0.0029 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-30.

Related

planr AGENTS.md compared with instructions from other repositories

planr AGENTS.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
planr AGENTS.mdinstructa/planrInstructions file7417d agoMITA734Codex, OpenCode
data-scientist copilot-instructions.mdrealnghon/data-scientistInstructions file24mo agoMITA373GitHub Copilot
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA9,719GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file143ktodayMITA7,461Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchainInstructions file149kyesterdayMITA4,680Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA5,516GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA3,093GitHub Copilot