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/suntay44/plannable/agents-mdgit clone --depth 1 https://github.com/suntay44/plannableWhat 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.00412 | $0.00412 |
| Opus 5 | $0.00206 | $0.00206 |
| Sonnet 5 | $0.00082 | $0.00082 |
| Haiku 4.5 | $0.00041 | $0.00041 |
Grade A, and why
plannable 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.
What it actually says
AGENTS.md
Plannable is a command-driven planning skill and CLI for AI coding agents.
Agent Rules
- This repo builds Plannable.
- Keep files small and agent-readable.
- Prefer examples over abstract theory.
- Do not create giant Markdown documents.
- Keep the human-facing plan short and scenario driven in
MASTER_PLAN.md. - Keep
.ai.mdfiles compressed but semantically readable. - Load only one compressed
plans/PART*_PLAN.ai.mdfile at a time. - All
.ai.mdplan parts must start with@PlannablePlan v0.1. - Do not call the compressed format PlanPack.
- Use
PlannablePlanas the format name. - Refer to domain-specific generation nudges as scenario hints, not presets or product templates.
- Do not use binary/base64/gzip as the default planning format.
- Mark a part complete only after adding evidence to
PLAN_EVIDENCE.md. - Prefer concrete verification artifacts: tests, screenshots, command output, changed file paths, or manual QA notes.
- Do not promise exact slash-command support where the platform does not support it.
- Be honest about platform-specific launchers.
Command Styles
Terminal CLI:
plannable create "CRM"
plannable run-next
plannable status
plannable verify
plannable evidence PART-001 "summary"
plannable complete PART-001
plannable doctor
plannable doctor --json
plannable repair
Codex:
$plannable create a CRM
$plannable run-next
$plannable status
$plannable verify
Claude Code:
/plannable create a CRM
/plannable run-next
/plannable status
/plannable verify
Cursor:
/plannable create a CRM
/plannable run-next
/plannable status
/plannable verify
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 · 66 lines · 412 tokens per session scan A d4520954ba9c
plannable AGENTS.md is an instructions file published in the GitHub repository suntay44/plannable (9 stars, last pushed 8d ago), licensed MIT. It adds 412 tokens to every session, about $0.0021 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.