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.
git 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/quick-review)<a href="https://agentmods.dev/commands/d-padmanabhan/agent-engineering-handbook/quick-review"><img src="https://agentmods.dev/badge/commands/d-padmanabhan/agent-engineering-handbook/quick-review.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.00010 | $0.00654 |
| Opus 5 | $0.00005 | $0.00327 |
| Sonnet 5 | $0.00002 | $0.00131 |
| Haiku 4.5 | $0.00001 | $0.00065 |
Grade A, and why
quick-review 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 6d 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QUICK REVIEW MODE ACTIVATED
You are now in QUICK REVIEW phase - a streamlined review for rapid iteration cycles.
[!NOTE] For comprehensive analysis, use
/self-reviewinstead. This command focuses on critical issues only.
Phase 1: Quick Context
-
Branch Status:
- Current branch (
git branch --show-current) - Files changed (
git diff main...HEAD --name-only | wc -l) - Diff summary (
git diff main...HEAD --stat)
- Current branch (
-
Recent Commits:
- Last 3 commits (
git log --oneline -3 main..HEAD)
- Last 3 commits (
Phase 2: Critical Checks Only
Run only the most critical checks:
Python:
ruff check .(critical errors only)mypy .orty .(type errors)bandit -r . -ll(high severity security issues)
Bash/Shell:
shellcheck(errors only, no warnings)
Go:
golangci-lint run --fast(critical issues)govulncheck ./...(vulnerabilities)
JavaScript/TypeScript:
eslint . --max-warnings=0(errors only)
Terraform:
terraform validatetflint(errors only)
General:
gitleaks detect --source .(secrets)
Phase 3: Critical Issues Only
Analyze git diff main...HEAD for:
Critical Issues (Must Fix)
- Security: Hardcoded secrets, injection risks, OWASP Top 10 violations
- Bugs: Logic errors, null pointer risks, data loss scenarios
- Breaking changes: API modifications without migration path
Skip Recommended/Optional issues for speed.
Phase 4: Quick Report
## Quick Review Summary
**Files Changed:** [count]
**Commits:** [count]
## Critical Issues Found
[File:line] Issue description
- Fix: [Brief suggestion]
## Status
✅ Ready for PR / ⚠️ Critical issues found
Phase 5: Quick Fixes (Optional)
If user requests fixes:
- Apply formatters only (
ruff format,gofmt,terraform fmt) - Re-stage formatted files
- Re-run critical checks
Constraints
⚠️ DO NOT:
- Modify files outside the current diff
- Perform unrelated Git operations
- Commit or push without explicit authorization
- Run comprehensive analysis (use
/self-reviewfor that)
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.
- 6d ago First seen · 119 lines · 10 tokens per session scan A 9d8bb7102d96
quick-review is a command published in the GitHub repository d-padmanabhan/agent-engineering-handbook (16 stars, last pushed 7d ago), licensed MIT. It adds 10 tokens to every session and 654 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
sdd-init
Initialize SDD context — detects project stack and bootstraps persistence backend.
review-branch
Review the current branch's diff against base by dispatching atomic-reviewer. No orchestration loop, no spec required — pre-flight before /commit pr or /commit merge.
init
Install the formatters this repository needs, with every command visible before it runs.
review-sdk-app
Review and validate a Claude Agent SDK application against best practices.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.
security-review
AI-powered security review of the current git diff (or specified paths). Dispatches the security-reviewer agent and prints findings grouped by severity.