Borrowing it
Nothing to install: this file belongs to appydave/appydave-tools. 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/appydave/appydave-tools/main/.claude/commands/progress.mdgit clone --depth 1 https://github.com/appydave/appydave-toolsWrote 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/appydave/appydave-tools/progress)<a href="https://agentmods.dev/commands/appydave/appydave-tools/progress"><img src="https://agentmods.dev/badge/commands/appydave/appydave-tools/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.1 | $0.00000 | $0.00341 |
| Opus 5 | $0.00000 | $0.00170 |
| Sonnet 5 | $0.00000 | $0.00068 |
| Haiku 4.5 | $0.00000 | $0.00034 |
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 yesterday.
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.
What it actually says
Quick Status
Provide a quick status summary of the AppyDave Tools project without deep codebase exploration.
Instructions
Read the following files and provide a concise summary:
- Read
CHANGELOG.md(last 2-3 versions only) - Read
docs/backlog.mdif it exists (requirements table) - Run
git log --oneline -10for recent commits - Run
git statusfor current working state
Output Format
## AppyDave Tools Status
### Current Version
- v0.X.Y (from CHANGELOG.md)
### Recently Completed
- [List last 3-5 features from CHANGELOG]
### In Progress / Pending
- [Any uncommitted changes from git status]
- [Any pending FRs from backlog if exists]
### Recent Commits
- [Last 5-7 commits from git log]
### Active Work Areas
- [Which systems have recent activity: DAM, GPT Context, etc.]
### Next Actions
- [What should happen next based on the current state]
Notes
- Keep it brief - this is a status check, not a deep dive
- Use CHANGELOG.md as source of truth for version history
- Check git status for uncommitted work
- If you need more detail, suggest running
/poor/devfor a full session
Related Agents
/po- Product Owner for requirements work/dev- Developer for implementation/uat- User acceptance testing/brainstorming-agent- Idea capture and clustering
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.
- yesterday First seen · 52 lines · 0 tokens per session scan A 25ea4ad52123
progress is a command published in the GitHub repository appydave/appydave-tools (9 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 341 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-09-05.
Other commands, from other repositories
gsd:quick
Execute a quick task with GSD guarantees (atomic commits, state tracking) but skip optional agents.
company-repo
Gestionar el repositorio Company Savia: crear, conectar, estado, sincronizar. El repositorio compartido de la empresa para conocimiento, mensajería y estado.
contribute
Contribuir mejoras, ideas o correcciones al repositorio de pm-workspace en GitHub.
backlog-sync
Sync local backlog with external PM tools (Azure DevOps, Jira, GitHub Issues).
gsd:pause-work
Create context handoff when pausing work mid-phase.
gsd:remove-phase
Remove a future phase from roadmap and renumber subsequent phases.