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.
Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add OthmanAdi/planning-with-files/plugin install planning-with-filesWrote 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/commands/othmanadi/planning-with-files/plan-doctor)<a href="https://agentmods.dev/commands/othmanadi/planning-with-files/plan-doctor"><img src="https://agentmods.dev/badge/commands/othmanadi/planning-with-files/plan-doctor/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.
<a href="https://agentmods.dev/commands/othmanadi/planning-with-files/plan-doctor"><img src="https://agentmods.dev/badge/commands/othmanadi/planning-with-files/plan-doctor.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00059 | $0.00352 |
| Opus 5 | $0.00030 | $0.00176 |
| Sonnet 5 | $0.00012 | $0.00070 |
| Haiku 4.5 | $0.00006 | $0.00035 |
Grade A, and why
plan-doctor 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 9d 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
Run the planning-with-files self-check against the current project directory.
Steps:
- Run the doctor script from the project root:
- Linux/macOS/Git Bash:
sh ${CLAUDE_PLUGIN_ROOT}/scripts/plan-doctor.sh - Windows without Git Bash on PATH: locate Git Bash via
git.exe(itsusr\bin\sh.exesibling) and run the same script with it.
- Linux/macOS/Git Bash:
- Report the PASS/WARN/FAIL lines to the user verbatim — they are designed to be read as-is.
- If any line reports FAIL, explain the matching remediation:
- resolver FAIL → inspect
.planning/.active_plancontent and plan dir names. - injection FAIL with a resolving plan → the hooks are silently dark; upgrading past v3.6.0 fixes the Windows-native-coreutils realpath cause. Also check
PLANNING_DISABLED. - tamper WARN → re-approve with
/plan-attestif the plan edit was intentional.
- resolver FAIL → inspect
- Do not attempt automatic fixes; this command is diagnostic only.
Why this exists: the mechanisms this skill relies on (hook injection, plan resolution) exit 0 and stay silent by design when something is off, so a broken install looks identical to "no plan yet". The doctor makes the difference visible in one pass.
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.
- 9d ago First seen · 21 lines · 59 tokens per session scan A b108ad5ea847
plan-doctor is a command published in the GitHub repository OthmanAdi/planning-with-files (26,736 stars, last pushed today), licensed MIT. It adds 59 tokens to every session and 352 once invoked, about $0.0003 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.
Other commands, from other repositories
health
One-line reliability verdict (OK / DEGRADED / FAILING) for Claude Code usage.
replay
Summarize one Agent Monitor session by id — header plus a concise transcript recap.
tail-events
Show the latest N ingested events with timestamp, eventtype, and toolname.
doctor
Health check for the dev environment and solana-ai-kit config — read-only, with one exact fix-it command per failure.
test-and-fix
Run tests and automatically fix common issues.
tidy
The structural baseline is empty. scripts/code-quality-baseline.json has no entries, so every gate is live: a new violation is now a hard failure with nothing to hide behind. That is the regime this session works in.