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
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.
git clone --depth 1 https://github.com/OthmanAdi/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/status)<a href="https://agentmods.dev/commands/othmanadi/planning-with-files/status"><img src="https://agentmods.dev/badge/commands/othmanadi/planning-with-files/status/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/status"><img src="https://agentmods.dev/badge/commands/othmanadi/planning-with-files/status.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.00017 | $0.00349 |
| Opus 5.5 | $0.00007 | $0.00140 |
| Sonnet 5.5 | $0.00003 | $0.00070 |
| Haiku 4.5 | $0.00002 | $0.00035 |
Grade A, and why
status 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 1mo 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
Read task_plan.md from the current project directory and display a compact status summary.
What to Show
- Current Phase: Extract from "## Current Phase" section
- Phase Progress: Count phases and their status (pending/in_progress/complete)
- Phase List: Show each phase with status icon
- Errors: Count entries in "## Errors Encountered" table if present
- Files Check: Confirm which planning files exist
Status Icons
[ ]or "pending" → ⏸️- "in_progress" → 🔄
[x]or "complete" → ✅- "failed" or "blocked" → ❌
Output Format
📋 Planning Status
Current: Phase {N} of {total} ({percent}%)
Status: {status_icon} {status_text}
{icon} Phase 1: {name}
{icon} Phase 2: {name} ← you are here
{icon} Phase 3: {name}
...
Files: task_plan.md {✓|✗} | findings.md {✓|✗} | progress.md {✓|✗}
Errors logged: {count}
If No Planning Files Exist
📋 No planning files found
Run /plan to start a new planning session.
Keep It Brief
This is a quick status check, not a full report. Show just enough to answer "where am I?" without re-reading all the files.
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.
- 1mo ago First seen · 50 lines · 17 tokens per session scan A 81d9b2d49a8c
status is a command published in the GitHub repository OthmanAdi/planning-with-files (27,467 stars, last pushed yesterday), licensed MIT. It adds 17 tokens to every session and 349 once invoked, about $0.0001 per session on Opus 5.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
genshijin-compress
A command for safely shortening Markdown or text files into the genshijin style.
valuation-methods
../../vertical-plugins/equity-research-core/commands/valuation-methods.md.
design-form
Design a form with the fewest fields that works, clear labels, and errors that help.
enum-udp
UDP scan + service follow-up — top ports first, full sweep only when justified.
configure-chiliforms
Build a ChiliForms embed (a form Chili Piper generates from a Concierge router) for a customer without a form of their own, and get a ready-to-paste snippet. Read-only.
audit
Adversarial, exhaustive review of the entire repository across code, tests, documentation, and configuration, with optional fixing in the same run. Assumes the code is incorrect until proven otherwise. This is the default command when the invocation names no other.