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.
npx agentmods add commands/design-and-deliver/claude-code-autoconfig/plan-progressgit clone --depth 1 https://github.com/design-and-deliver/claude-code-autoconfigWrote 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/design-and-deliver/claude-code-autoconfig/plan-progress)<a href="https://agentmods.dev/commands/design-and-deliver/claude-code-autoconfig/plan-progress"><img src="https://agentmods.dev/badge/commands/design-and-deliver/claude-code-autoconfig/plan-progress.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00752 |
| Opus 5 | $0.00000 | $0.00376 |
| Sonnet 5 | $0.00000 | $0.00150 |
| Haiku 4.5 | $0.00000 | $0.00075 |
Grade A, and why
plan-progress 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 3d 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan Progress
Show, at a glance, where the project's phased plan doc(s) stand — the read-only twin of
/continue. /continue runs the next unchecked substep; this just shows the map, cheaply,
without spending tokens on execution.
It reads the plan-authoring format (.claude/rules/plan-authoring.md): phases
(## Phase N — title), substeps (### ☑|☐ N.k · S|M|L · ~time — title), and a ## Ledger
that marks a doc as an executable plan rather than a design doc. Because the effort tags carry
time estimates, the percentage is effort-weighted, not a naive substep count.
Step 1: run the deterministic digest
All parsing and arithmetic is done by a pure-node script — no LLM math:
node .claude/scripts/plan-progress.js
It scans docs/, .claude/plans/, and the repo root for ## Ledger plan docs, and prints
ready-to-show Markdown (one dashboard per plan, in-progress plans first).
Step 2: present the output
Show the script's Markdown output as-is — it already renders the way it should: strikethrough
on completed substeps, a bold ▶ … ← you are here on the current step, a ▓▓▓░░ bar with the
percent, done/total substeps, and ~time left. The view is the value; don't rewrite it into a
paragraph.
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.
- 3d ago First seen · 54 lines · 0 tokens per session scan A 7aeaf0356653
plan-progress is a command published in the GitHub repository design-and-deliver/claude-code-autoconfig (2 stars, last pushed 5d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 752 tokens. 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-31.
Other commands, from other repositories
project-recap
Generate a visual project recap for context switching.
os-meeting
快速创建和管理AI团队会议.
workspace
Testany Workspace, 管理工作空间，成员权限，团队组织.
standup
Show a daily standup summary with completed, in-progress, and blocked tasks across all active epics.
m-task-planner
Target: $ARGUMENTS (Default: requirement document(s) discovered in the project).
triage-issues
Launch the Issue Triage Agent (Haiku) to categorize and prioritize GitHub issues.