pwf-status

pwf-status is a command for Claude Code, OpenCode from OthmanAdi/planning-with-files. It costs 21 tokens per session (80 once invoked), scanned A, original, MIT.

A command that displays the current status of a planning-with-files plan, including its phase and completion counts.

In plain words
What is it for?
It helps check the plan ID, mode, attestation, current phase, completed phases, and nested-project conflicts.
Why use it?
It gives a compact view of progress and reported project conflicts without changing any files.

Command for Claude CodeOpenCode

Written for OpenCode and Claude Code: installed under .opencode/, but also a Claude Code command (commands/*.md).

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

Good fit It helps check the plan ID, mode, attestation, current phase, completed phases, and nested-project conflicts.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/othmanadi/planning-with-files/pwf-status
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,707 stars · on GitHub · skills.sh

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.

Clone the repo
git clone --depth 1 https://github.com/OthmanAdi/planning-with-files

Made for: Claude Code, OpenCode.

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 pwf-status

README.md
[![agentmods](https://agentmods.dev/badge/commands/othmanadi/planning-with-files/pwf-status.svg)](https://agentmods.dev/commands/othmanadi/planning-with-files/pwf-status)
Your own site
<a href="https://agentmods.dev/commands/othmanadi/planning-with-files/pwf-status"><img src="https://agentmods.dev/badge/commands/othmanadi/planning-with-files/pwf-status.svg" alt="Measured on agentmods" height="20"></a>
Per session 21 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 80 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00021 $0.00080
Opus 5 $0.00010 $0.00040
Sonnet 5 $0.00004 $0.00016
Haiku 4.5 $0.00002 $0.00008

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

Security

Grade A, and why

pwf-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 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.

.opencode/commands/pwf-status.md · 5 lines

What it actually says

Call the pwf_status tool and present the result as one compact block: plan id, mode, attested yes or no, current phase, phases complete / total with the in_progress count, and any nested-project conflicts it reports. Do not modify any file.

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 · 5 lines · 21 tokens per session scan A bf8a12782a25

Subscribe to this mod's changes

pwf-status is a command published in the GitHub repository OthmanAdi/planning-with-files (26,707 stars, last pushed yesterday), licensed MIT. It adds 21 tokens to every session and 80 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-09-03.