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.
Borrowing it
Nothing to install: this file belongs to OthmanAdi/planning-with-files. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/OthmanAdi/planning-with-files/master/AGENTS.mdgit 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/instructions/othmanadi/planning-with-files/agents-md)<a href="https://agentmods.dev/instructions/othmanadi/planning-with-files/agents-md"><img src="https://agentmods.dev/badge/instructions/othmanadi/planning-with-files/agents-md/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/instructions/othmanadi/planning-with-files/agents-md"><img src="https://agentmods.dev/badge/instructions/othmanadi/planning-with-files/agents-md.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.01090 | $0.01090 |
| Opus 5.5 | $0.00436 | $0.00436 |
| Sonnet 5.5 | $0.00218 | $0.00218 |
| Haiku 4.5 | $0.00109 | $0.00109 |
Grade A, and why
planning-with-files 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 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.
How it starts
The opening of the file, as written. The whole thing — 29 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md, planning-with-files maintainer rules
For any agent doing releases, merges or issue work in this repository. The code and scripts/ are discoverable; this file holds the decisions that are not.
Authorship
- Contributor commits keep the contributor as
Author:. Merge withgit fetch origin pull/N/head:pr-N && git cherry-pick <sha>orgh pr merge --rebase. Nevergit merge --squasha contributor PR: it reassigns their commit to whoever runs the local commit, which happened once in the v2.40.1 cycle. Squash only your own WIP before pushing. - Release and maintenance commits are authored by OthmanAdi alone, Conventional Commits (
fix:,feat:,release:,docs:), noCo-Authored-By. Contributors are credited in the CHANGELOG### Thankssection and inCONTRIBUTORS.md, never in trailers. - No
--no-verify. No force push to master except tag ref updates and history corrections Adi explicitly authorised.
Release flow
- Read the issue and the PR in full (
gh issue view N,gh pr view N). Reproduce the claim against the code. Audit the diff for supply-chain vectors (new dependencies, install scripts, bin shims, files in the install path). Comment on the issue the moment it is confirmed, with the planned fix; the closing comment comes after shipping. Never batch all communication to the end. python -m pytest tests/ -qis green before and after the merge.- Merge the contributor commits as above, then one release commit on top: CHANGELOG entry, CONTRIBUTORS.md (entry, total count, date), README version badge and releases table row, version bump.
- Bump with
python scripts/bump-version.py X.Y.Z(--dry-runfirst), never by hand.tests/test_skill_md_version_parity.pydefines the parity set (19 tracked files plus the gitignoredclawhub-upload/SKILL.mdwhen present); the script and the test are the source of truth, not any list in prose. Deliberately lagging:.continueand.gemini(bump only on an explicit scope decision),.kiro(own-kiroscheme),.pi/.../SKILL.md(no version field; the Pi version is itspackage.json, which is in the set). The bundled Pi extension's ownpackage.jsonmoves only when that extension changed. - Tag
vX.Y.Zon the release commit, push master and the tag, thengh release create vX.Y.Z --title "vX.Y.Z - <short description>" --notes "<what changed, then Thanks>". - Distribution is manual after every release. ClawHub:
python scripts/build-clawhub-upload.py, thenpython scripts/build-clawhub-upload.py --verify(the staged folder must match the tracked inventory), then upload the wholeclawhub-upload/folder at clawhub.io (its SSL certificate may be expired; proceed through the warning). npm:npm publishfrom.pi/skills/planning-with-files/(the unscoped packageplanning-with-files, Adi's account; the abandoned@tomxprime/planning-with-filesandpi-planning-with-filesare never touched). skills.sh andnpx skillspull master on their own; the Anthropic marketplace reflects the ClawHub upload. - Comment on the PR and the issue (contributor's @handle, the version that fixes it, root cause and mechanism, "you are in CONTRIBUTORS.md" when true, the commit SHA so it auto-links), then close what GitHub did not close.
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 · -133 lines · -1,146 tokens per session 651067324f17
- 1mo ago Changed · +42 tokens per session c6aeaa9d7fec
- 1mo ago First seen · 162 lines · 2,194 tokens per session scan A cae4bfdd4e06
planning-with-files AGENTS.md is an instructions file published in the GitHub repository OthmanAdi/planning-with-files (27,535 stars, last pushed 2d ago), licensed MIT. It adds 1,090 tokens to every session, about $0.0044 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 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).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.