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/agents-mdgit clone --depth 1 https://github.com/nickmisasi/plannerWhat 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.00980 | $0.00980 |
| Opus 5 | $0.00490 | $0.00490 |
| Sonnet 5 | $0.00196 | $0.00196 |
| Haiku 4.5 | $0.00098 | $0.00098 |
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 2d 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 — 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.yamlat the start of every session - Read
session.mdwhen resuming work on an idea — it contains full conversation state - Update
session.mdat the end of every session with progress, decisions, open questions, and next steps - Update
registry.yamlwhen 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
mainbranch 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
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.
- 2d ago First seen · 103 lines · 980 tokens per session scan A 5054ae27acfb
planner AGENTS.md is an instructions file published in the GitHub repository nickmisasi/planner (5 stars, last pushed 4mo ago), licensed MIT. It adds 980 tokens to every session, about $0.0049 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
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.
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).
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.