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/self-review)<a href="https://agentmods.dev/commands/d-padmanabhan/agent-engineering-handbook/self-review"><img src="https://agentmods.dev/badge/commands/d-padmanabhan/agent-engineering-handbook/self-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.00014 | $0.02050 |
| Opus 5 | $0.00007 | $0.01025 |
| Sonnet 5 | $0.00003 | $0.00410 |
| Haiku 4.5 | $0.00001 | $0.00205 |
Grade A, and why
self-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 8d 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 — 241 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SELF CODE REVIEW MODE ACTIVATED
You are now in SELF REVIEW phase - performing a comprehensive local code review comparing the current branch to main, following the structured review approach from 100-core.mdc and 010-workflow.mdc.
[!IMPORTANT] This is a read-only analysis. No commits or pushes will be made without explicit user authorization (see
020-agent-audit.mdc).
Phase 1: Context Gathering & Audit Setup
Audit Requirements (from 020-agent-audit.mdc):
- Record baseline:
HEADSHA, branch name, timestamp - For critical tasks, write/append a full audit report
- For routine tasks, a lightweight entry (or no report) is acceptable
[!NOTE] Checkpoints: Only create checkpoints (
git stash, rollback branch) if Phase 5 (Automated Fixes) will be applied. For read-only analysis, baseline recording is sufficient.Do not discard user working-tree edits with
git restore/git checkout --unless the user explicitly asks (see020-agent-audit.mdc).
-
Branch Information:
- Current branch name (
git branch --show-current) - Base branch (default:
main) - Baseline SHA (
git rev-parse HEAD) - Commits ahead of base (
git log --oneline main..HEAD) - Files changed (
git diff main...HEAD --name-only)
- Current branch name (
-
Change Summary:
- Show staged changes (
git diff --cached --stat) - Show unstaged changes (
git diff --stat) - Ignore files/folders listed in
.gitignore - Generate diff summary:
git diff main...HEAD --stat
- Show staged changes (
-
Recent Commit History:
- Display last 3-5 commits:
git log --oneline -5 main..HEAD - Show commit messages to understand change context
- Display last 3-5 commits:
Phase 2: Static Analysis
Run appropriate linters and analyzers based on project language:
Python:
ruff check .(linting)ruff format --check .(format check)mypy .orty .(type checking)pylint(aim for score ≥9.5)bandit -r .(security scanning)pip-audit(dependency vulnerabilities)tox(if applicable)
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.
- 8d ago First seen · 241 lines · 14 tokens per session scan A 8a5e4b2a9524
self-review is a command published in the GitHub repository d-padmanabhan/agent-engineering-handbook (16 stars, last pushed yesterday), licensed MIT. It adds 14 tokens to every session and 2,050 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
devkit.github.review-pr
Provides comprehensive GitHub pull request review with code quality, security, and best practices analysis. Use when reviewing a PR before merging.
speckit.spex.submit
Push and create PR for team review, with optional watch mode for CI monitoring.
git
The pre-finish status: branch, hygiene findings, message checks, workflow lint, template state.
merge-conflict-analysis
You are analyzing merge conflicts for PR #${{ pr-number }}.
code-review
Code review for branch changes. Analyzes git diff between branches with multi-level depth (low/medium/high). Matches changes against task description. Returns structured report with severity levels and verdict.
repo-audit
Audit a codebase (local or remote GitHub/GitLab) against architecture principles and requirements, surfacing drift, risk, and missing decisions.