plan

plan is a command for coding agents from OthmanAdi/planning-with-files. It costs 11 tokens per session (91 once invoked), scanned A, original, MIT.

A command that starts or resumes a file-based planning process for the current project. It creates or uses files that record the plan, discoveries, and progress.

In plain words
What is it for?
It helps agents find the project root, initialize planning files, read existing task information, and continue multi-step work.
Why use it?
It keeps the agent’s working context on disk, so a complex task can continue after interruptions or across sessions.

Command

Part of the planning-with-files plugin — 6 skills, 15 commands, 6 hooks shipped together

About the project

OthmanAdi/planning-with-files is a planning system that stores an AI coding agent's task plan, findings, and progress in project files so the work can be recovered after context resets, crashes, or compaction. It is for long-running coding tasks across many agent tools, including Claude Code, Codex CLI, and Cursor. The catalogue entries are the project's commands, hooks, skills, plugin, and instruction for maintaining those planning files.

OthmanAdi/planning-with-files · 26,613 stars · on GitHub

Install

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.

agentmods
npx agentmods add commands/othmanadi/planning-with-files/plan
Clone the repo
git clone --depth 1 https://github.com/OthmanAdi/planning-with-files

Or install planning-with-files, the plugin that ships this one along with the rest of its 6 skills, 15 commands, 6 hooks.

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.

agentmods badge for plan

README.md
[![agentmods](https://agentmods.dev/badge/commands/othmanadi/planning-with-files/plan.svg)](https://agentmods.dev/commands/othmanadi/planning-with-files/plan)
Your own site
<a href="https://agentmods.dev/commands/othmanadi/planning-with-files/plan"><img src="https://agentmods.dev/badge/commands/othmanadi/planning-with-files/plan.svg" alt="Measured on agentmods" height="20"></a>
Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 91 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.00011 $0.00091
Opus 5 $0.00005 $0.00046
Sonnet 5 $0.00002 $0.00018
Haiku 4.5 $0.00001 $0.00009

Measured 4d ago against content hash 88b547dfe5c7, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

plan 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 4d 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.

.hermes/commands/plan.md · 11 lines

What it actually says

Load the planning-with-files skill and follow it.

  1. Determine the actual project root for the current task.
  2. Run planning_with_files_init with cwd set to that project root.
  3. Read task_plan.md, findings.md, and progress.md from that same directory.
  4. Begin or continue the planning workflow.
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.

  1. 4d ago First seen · 11 lines · 11 tokens per session scan A 88b547dfe5c7

Subscribe to this mod's changes

plan is a command published in the GitHub repository OthmanAdi/planning-with-files (26,613 stars, last pushed yesterday), licensed MIT. It adds 11 tokens to every session and 91 once invoked, about $0.0001 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-30.