What is planner CLAUDE.md?

Instructions for an AI-first planning repository, where an agent helps users research projects and write specifications instead of users editing the files directly. They describe the repository layout, startup checks, planning commands, and helper agents.

Use them to explore a codebase, research a topic, register projects, develop ideas, and create detailed feature plans.

They give planning work a consistent structure and make project decisions, research, and ideas easier to organize and track.

How nickmisasi/planner configures Claude Code

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/CLAUDE.md

Clone the repo

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

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.

README.md

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

Your own site

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

Your own site · 80×15

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

Per session 4,126 This file is loaded in full into every session.

When invoked 4,126 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.04126	$0.04126
Opus 5.5	$0.01650	$0.01650
Sonnet 5.5	$0.00825	$0.00825
Haiku 4.5	$0.00413	$0.00413

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

Security

Grade A, and why

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

CLAUDE.md · 339 lines

How it starts

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

Planning Repository — Agent Instructions

This is an AI-first planning repository. The user interacts exclusively through AI agents — they never read files directly. Your job is to help the user plan, research, and spec out features and projects across their codebases.

Repository Structure

planning/
├── CLAUDE.md              ← You are here. Read this first, always.
├── registry.yaml          ← Master index of ALL projects and their ideas
├── bin/
│   └── planning           ← CLI for scaffolding and registry ops (saves context window)
├── .claude/
│   ├── settings.json      ← Hooks configuration
│   ├── agents/
│   │   ├── explorer.md    ← Codebase exploration sub-agent
│   │   ├── researcher.md  ← Web/doc research sub-agent
│   │   └── planner.md     ← Spec analysis and planning sub-agent
│   └── skills/
│       └── <skill-name>/
│           └── SKILL.md   ← Slash command definition (with YAML frontmatter)
├── projects/
│   └── <project-slug>/
│       ├── project.yaml   ← Project metadata, repo URLs, description
│       ├── context.md     ← Living doc: architecture, decisions, gotchas
│       └── ideas/
│           └── <NNN>-<slug>/
│               ├── spec.md         ← The specification / PRD (current milestone)
│               ├── research.md     ← Research notes and findings (current milestone)
│               ├── session.md      ← Conversation state for cross-session pickup
│               ├── assumptions.md  ← Tracked assumptions with confidence scores (current milestone)
│               ├── IMPL_ORCHESTRATION_PLAN.md ← Cross-repo phase ordering and commit checkpoints (when implementing)
│               ├── MILESTONES.md   ← Index of completed milestones (if any)
│               ├── spikes/         ← Experiment code (current milestone)
│               └── milestones/     ← Archived milestone folders
│                   └── mN-<slug>/
│                       ├── SUMMARY.md      ← Concise milestone summary (read this first)
│                       ├── spec.md         ← Frozen spec from that milestone
│                       ├── research.md     ← Frozen research
│                       ├── assumptions.md  ← Frozen assumptions
│                       ├── session.md      ← Final session state
│                       ├── IMPL_ORCHESTRATION_PLAN.md ← Archived orchestration plan (if created)
│                       └── spikes/         ← Archived spikes
└── templates/             ← Scaffolding templates (consumed by bin/planning)

Read the full file on GitHub · 339 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 · 339 lines · 4,126 tokens per session scan A 3d3fefbde896

Subscribe to this mod's changes

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

Planning

planner CLAUDE.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
planner CLAUDE.mdnickmisasi/planner	Instructions file	5	6mo ago	MIT	A	4,126	Claude Code
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 Claude Code