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/d-padmanabhan/agent-engineering-handbook/check-progressgit clone --depth 1 https://github.com/d-padmanabhan/agent-engineering-handbookWrote 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/d-padmanabhan/agent-engineering-handbook/check-progress)<a href="https://agentmods.dev/commands/d-padmanabhan/agent-engineering-handbook/check-progress"><img src="https://agentmods.dev/badge/commands/d-padmanabhan/agent-engineering-handbook/check-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.00020 | $0.01741 |
| Opus 5 | $0.00010 | $0.00870 |
| Sonnet 5 | $0.00004 | $0.00348 |
| Haiku 4.5 | $0.00002 | $0.00174 |
Grade A, and why
check-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 5d 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 — 249 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CHECK PROGRESS MODE ACTIVATED
Review current work progress without staging or committing. Fix issues, run quality checks, and propose commit messages using the core rule (${HANDBOOK_ROOT}/rules/100-core.mdc) and Git workflow skill (${HANDBOOK_ROOT}/skills/git-workflow/SKILL.md).
[!IMPORTANT] Fix mode. Fix errors and formatting issues, then report what was fixed.
No staging, committing, or pushing will be performed.
Phase 1: Change Detection
-
Identify Modified Files:
- Show staged changes (
git diff --cached --name-only) - Show unstaged changes (
git diff --name-only) - Ignore files/folders listed in
.gitignore - Count files by type (Python, Bash, Go, JS/TS, Terraform, etc.)
- Show staged changes (
-
Branch Context:
- Current branch name (
git branch --show-current) - Extract Jira ticket from branch name (if present, e.g.,
feat/OCFN-1443-fix-auth) - Commits ahead of base (
git log --oneline main..HEAD)
- Current branch name (
Phase 2: Quality Checks
Run appropriate formatters and linters based on modified files only.
[!IMPORTANT] Do not stage anything. Do not run commands that modify the git index.
Python Files
Fix, then validate:
ruff format <files>(format)ruff check <files> --fix(lint autofix where safe)black <files>(format, if used in repo)isort <files>(imports, if used in repo)mypy <files>orty <files>(type checking)pylint <files>(aim for score ≥9.0, prefer ≥9.5)bandit -r <files> -ll(security scanning - high/low severity)
Bash/Shell Files
Fix, then validate:
shfmt -w -i 2 -ci -sr -bn <files>(format)shellcheck <files>(lint)
Go Files
Fix, then validate:
gofmt -w -s <files>(format)go vet ./...staticcheck ./...golangci-lint run ./...govulncheck ./...
JavaScript/TypeScript Files
Fix, then validate:
eslint <files> --fix(if configured)eslint <files> --max-warnings=0tsc --noEmit(if TypeScript)npm audit(ifpackage.jsonexists)
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.
- 5d ago First seen · 249 lines · 20 tokens per session scan A 9f72a24058b9
check-progress is a command published in the GitHub repository d-padmanabhan/agent-engineering-handbook (16 stars, last pushed 5d ago), licensed MIT. It adds 20 tokens to every session and 1,741 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.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.