A command that checks a project’s files, tests, documentation, and recent Git activity, then reports what is complete and what remains.

Use it to review source files, test coverage, documentation, recent commits, and file counts.

It gives you a current project status without manually inspecting each part of the codebase.

progress — Command by TheDecipherist

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.

agentmods

npx agentmods add commands/thedecipherist/claude-code-mastery-project-starter-kit/progress

Clone the repo

git clone --depth 1 https://github.com/TheDecipherist/claude-code-mastery-project-starter-kit

Made for: Claude Code.

Per session 12 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 513 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

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.

Model	Per session	Once invoked
Fable 5	$0.00012	$0.00513
Opus 5	$0.00006	$0.00257
Sonnet 5	$0.00002	$0.00103
Haiku 4.5	$0.00001	$0.00051

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

Security

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 2d 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.

.claude/commands/progress.md · 62 lines

What it actually says

Project Progress

Check the actual state of all components and report status.

Instructions

Read project-docs/ARCHITECTURE.md for project context (if it exists)
Check the src/ directory structure
Check the tests/ directory for test coverage
Check recent git activity

Shell Commands to Run

echo "=== Source Files ==="
find src/ -name "*.ts" -o -name "*.tsx" | head -30 2>/dev/null || echo "No src/ directory"

echo ""
echo "=== Test Files ==="
find tests/ -name "*.test.*" -o -name "*.spec.*" | head -30 2>/dev/null || echo "No test files"

echo ""
echo "=== Recent Activity (Last 7 Days) ==="
git log --oneline --since="7 days ago" 2>/dev/null | head -15 || echo "No recent commits"

echo ""
echo "=== File Count by Type ==="
find src/ -name "*.ts" 2>/dev/null | wc -l | xargs -I{} echo "TypeScript: {} files"
find src/ -name "*.js" 2>/dev/null | wc -l | xargs -I{} echo "JavaScript: {} files"
find tests/ -name "*.test.*" 2>/dev/null | wc -l | xargs -I{} echo "Tests: {} files"

Output Format

Area	Files	Status	Notes
Source code	N files	...	...
Tests	N files	...	...
Documentation	...	...	...

RuleCatch Report

Metric	Value
Violations (this session)	...
Critical violations	...
Most violated rule	...
Files with violations	...

If the RuleCatch MCP server is available: query for session summary and populate the table above. If no MCP available: show "Install RuleCatch for violation tracking — npx @rulecatch/mcp-server init"

Next Actions (Priority Order)

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.

2d ago First seen · 62 lines · 12 tokens per session scan A 2ed80169d020

Subscribe to this mod's changes

progress is a command published in the GitHub repository TheDecipherist/claude-code-mastery-project-starter-kit (337 stars, last pushed 2mo ago), licensed MIT. It adds 12 tokens to every session and 513 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-08-30.

Project management

template

Manage issue templates for streamlined issue creation.

gastownhall/beads · 0 tokens

speckit.auto

Automatically execute the four core phases of the Spec-Driven Development (SDD) pipeline: specify → plan → tasks → implement, in strict sequential order.

VisActor/VChart · 31 tokens

daily-priorities

Query DIGI Jira via the Atlassian MCP to build a prioritized daily work plan. The report has two parts: suggested priorities (the recommendation) and full context (everything you need to evaluate whether the suggestions are right and what else is on the docket).

DIGI-UW/OpenELIS-Global-2 · 0 tokens

progress