What is planner AGENTS.md?

A set of instructions for an AI-first repository used to track project ideas, specifications, and research. It tells agents where to find the main index and the files for each project or idea.

It helps agents resume projects, review ideas, read planning documents, and follow the repository's required workflow.

It gives agents a consistent way to understand the repository before continuing work, reducing missed context and incorrect starting points.

How nickmisasi/planner configures Codex and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to nickmisasi/planner. 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/nickmisasi/planner/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/nickmisasi/planner

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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/nickmisasi/planner/agents-md/github.svg)](https://agentmods.dev/instructions/nickmisasi/planner/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/nickmisasi/planner/agents-md"><img src="https://agentmods.dev/badge/instructions/nickmisasi/planner/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/nickmisasi/planner/agents-md"><img src="https://agentmods.dev/badge/instructions/nickmisasi/planner/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 980 This file is loaded in full into every session.

When invoked 980 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.

Model	Per session	Once invoked
Fable 5.1	$0.00980	$0.00980
Opus 5.5	$0.00392	$0.00392
Sonnet 5.5	$0.00196	$0.00196
Haiku 4.5	$0.00098	$0.00098

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

Security

Grade A, and why

planner 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 2mo 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 · 103 lines

How it starts

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

Planning Repository — Agent Instructions (Universal)

This file provides instructions for non-Claude AI agents (Copilot, Cursor, Windsurf, etc.). For Claude Code, see CLAUDE.md which has richer, Claude-specific instructions including hooks and skills.

What This Repository Is

An AI-first planning repository for tracking project ideas, specs, and research. The user interacts exclusively through AI agents — they never read files directly.

Commands to Run First

# Always start by reading the master index
cat registry.yaml

# To resume a specific project
cat projects/<project-slug>/project.yaml
cat projects/<project-slug>/context.md

# To resume a specific idea
cat projects/<project-slug>/ideas/<NNN>-<slug>/session.md
cat projects/<project-slug>/ideas/<NNN>-<slug>/spec.md
cat projects/<project-slug>/ideas/<NNN>-<slug>/assumptions.md
# If the idea is implementing or coordinating execution
cat projects/<project-slug>/ideas/<NNN>-<slug>/IMPL_ORCHESTRATION_PLAN.md

Repository Structure

planning/
├── CLAUDE.md / AGENTS.md  ← Agent instructions
├── registry.yaml          ← Master index of all projects and ideas
├── projects/
│   └── <project-slug>/
│       ├── project.yaml   ← Project metadata, repo URLs
│       ├── context.md     ← Living architecture/decision notes
│       └── ideas/
│           └── <NNN>-<slug>/
│               ├── spec.md         ← Specification / PRD
│               ├── research.md     ← Research notes
│               ├── session.md      ← Cross-session conversation state
│               ├── assumptions.md  ← Tracked assumptions with confidence scores
│               ├── IMPL_ORCHESTRATION_PLAN.md ← Cross-repo phase sequencing and commit checkpoints
│               └── spikes/         ← Experiment code
└── templates/             ← Templates for scaffolding new projects/ideas

Key Behaviors

Always Do

Read registry.yaml at the start of every session
Read session.md when resuming work on an idea — it contains full conversation state
Update session.md at the end of every session with progress, decisions, open questions, and next steps
Update registry.yaml when creating or changing the status of projects/ideas
Use templates from templates/ when scaffolding new projects or ideas
Cite sources in research.md — include URLs, file paths, commit hashes
For this planning repo itself, stay on the main branch unless the user explicitly asks for a different workflow
Make small, logical local commits as planning-repo changes develop to preserve iteration history and recovery points

Read the full file on GitHub · 103 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.

2mo ago First seen · 103 lines · 980 tokens per session scan A 5054ae27acfb

Subscribe to this mod's changes

planner AGENTS.md is an instructions file published in the GitHub repository nickmisasi/planner (5 stars, last pushed 6mo ago), licensed MIT. It adds 980 tokens to every session, about $0.0039 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.

Building agents Planning

planner AGENTS.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
planner AGENTS.mdnickmisasi/planner	Instructions file	5	6mo ago	MIT	A	980	Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	yesterday	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

planner: Instructions file for Codex