Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/nickmisasi/planner/claude-mdgit clone --depth 1 https://github.com/nickmisasi/plannerWrote 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/nickmisasi/planner/claude-md)<a href="https://agentmods.dev/instructions/nickmisasi/planner/claude-md"><img src="https://agentmods.dev/badge/instructions/nickmisasi/planner/claude-md.svg" alt="Measured on agentmods" 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 | $0.04126 | $0.04126 |
| Opus 5 | $0.02063 | $0.02063 |
| Sonnet 5 | $0.00825 | $0.00825 |
| Haiku 4.5 | $0.00413 | $0.00413 |
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 3d 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.
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)
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.
- 3d ago First seen · 339 lines · 4,126 tokens per session scan A 3d3fefbde896
planner CLAUDE.md is an instructions file published in the GitHub repository nickmisasi/planner (5 stars, last pushed 4mo ago), licensed MIT. It adds 4,126 tokens to every session, about $0.0206 per session on Opus 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).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
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.
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 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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.