Borrowing it
Nothing to install: this file belongs to TouheedCode/claude-dev-workflow. 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/TouheedCode/claude-dev-workflow/master/.claude/commands/progress.mdgit clone --depth 1 https://github.com/TouheedCode/claude-dev-workflowWrote 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/touheedcode/claude-dev-workflow/progress)<a href="https://agentmods.dev/commands/touheedcode/claude-dev-workflow/progress"><img src="https://agentmods.dev/badge/commands/touheedcode/claude-dev-workflow/progress/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/touheedcode/claude-dev-workflow/progress"><img src="https://agentmods.dev/badge/commands/touheedcode/claude-dev-workflow/progress.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.00000 | $0.00742 |
| Opus 5.5 | $0.00000 | $0.00297 |
| Sonnet 5.5 | $0.00000 | $0.00148 |
| Haiku 4.5 | $0.00000 | $0.00074 |
Grade A, and why
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 2mo 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/progress — Visual Phase Progress
Arguments
$ARGUMENTS— Optional: story ID (e.g., "US-001"). If omitted, reads from.phase-context.json.
Instructions
You are generating a visual progress report showing which phases are complete, in-progress, or pending for the current feature.
Input: $ARGUMENTS
Step 1: Load State
- Read
.phase-context.jsonfor the story ID andcompletedPhasesarray - Read the plan at
docs/plans/PLAN-{story-ID}.mdto get the full phase list - Run
git log main..HEAD --onelineto detect any uncommitted phase work
Determine the status of each phase:
- Done — listed in
completedPhasesand has a matching commit - Active — has deliverable files on disk but not yet in
completedPhases(work in progress) - Pending — no files created yet
Step 2: Generate Progress Display
Print an ASCII progress bar and phase table:
US-001: Todo List Management
================================================
Progress: [################........] 4/7 phases (57%)
Phase Status Title Files Tests
----- ------- ----------------------- ----- -----
1 [done] Presentational UI 6 12
2 [done] API Client & Mocks 3 -
3 [done] Smart Components 3 4
4 [done] Repository Layer 4 8
5 [ ] Service Layer - -
6 [ ] Controller Layer - -
7 [ ] Integration - -
Next step: /implement Phase 5
================================================
Active phase (work in progress):
Progress: [################=>......] 4.5/7 phases
5 [>>>>] Service Layer 1/2 0/8
Step 3: Show Phase Dependencies
If the next pending phase has dependencies, show them:
Dependencies for Phase 5:
Phase 4 (Repository Layer) [done] -- provides repository interfaces
If dependencies are unmet:
BLOCKED: Phase 5 requires Phase 4 to be completed first.
Run: /implement Phase 4
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.
- 2mo ago First seen · 96 lines · 0 tokens per session scan A 7ae9d8bdb1a8
progress is a command published in the GitHub repository TouheedCode/claude-dev-workflow (2 stars, last pushed 16d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 742 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
status
A project-status command that checks a code repository and its supporting project notes. The supplied description is in Chinese and lists checks for Git, a memory bank, dependencies, environment settings, components, and conflicts.
pm
A product-management command that turns a short or unclear request into a written product requirement. It uses the project's existing context to define scope, acceptance criteria, priorities, decisions, and assumptions.
task
A command for breaking work into small, trackable tasks and managing their status. It defines states such as pending, in progress, completed, and blocked.
audit-agents-skills
Audit quality of agents, skills, and commands in a Claude Code project.
audit-repo-docs
Audit repository documentation against 85+ best practices from claude-code-ultimate-guide.
boldguy-linkedin-answer
Draft a LinkedIn comment on a post, referencing the guide's relevant section, in Flow style with AI markers removed.