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-attest)<a href="https://agentmods.dev/commands/othmanadi/planning-with-files/plan-attest"><img src="https://agentmods.dev/badge/commands/othmanadi/planning-with-files/plan-attest/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-attest"><img src="https://agentmods.dev/badge/commands/othmanadi/planning-with-files/plan-attest.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.00064 | $0.00456 |
| Opus 5.5 | $0.00026 | $0.00182 |
| Sonnet 5.5 | $0.00013 | $0.00091 |
| Haiku 4.5 | $0.00006 | $0.00046 |
Grade A, and why
plan-attest 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
Run the plan attestation helper for the active plan.
Steps:
- Resolve the active plan: prefer
${PLAN_ID}env var, then.planning/.active_plan, then newest.planning/<dir>/. If the current directory is itself a valid.planning/<slug>/directory, use itstask_plan.md. Otherwise use legacy./task_plan.md. - Compute the SHA-256 of the resolved
task_plan.md. - Write the hex digest to
.planning/<active-plan>/.attestation(parallel-plan mode) or./.plan-attestation(legacy mode). - Confirm to the user with the short hash (first 12 hex chars) and the storage path.
An explicit ${PLAN_ID} or ${PWF_PLAN_ROOT} that does not resolve exits with an error. It never falls back to another plan.
Implementation:
- On Linux/macOS/Git Bash:
sh ${CLAUDE_PLUGIN_ROOT}/scripts/attest-plan.sh - On Windows PowerShell plugin installs:
& "$env:CLAUDE_PLUGIN_ROOT\scripts\attest-plan.ps1" - On Windows PowerShell standalone installs:
& "$env:USERPROFILE\.claude\skills\planning-with-files\scripts\attest-plan.ps1"
Flags:
--show— print the currently stored hash and where it lives.--clear— remove the attestation (re-open the plan to free editing).
After running this command, every UserPromptSubmit and PreToolUse hook fire compares task_plan.md against the stored hash. If they diverge, the hook emits [PLAN TAMPERED — injection blocked] instead of feeding plan content into the model. Re-run /plan-attest whenever you intentionally edit and re-approve the plan.
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 Changed · +2 lines a5e6adb867c2
- 1mo ago First seen · 25 lines · 64 tokens per session scan A ae3f009bdfd3
plan-attest is a command published in the GitHub repository OthmanAdi/planning-with-files (27,535 stars, last pushed 2d ago), licensed MIT. It adds 64 tokens to every session and 456 once invoked, about $0.0003 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.