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 skills add theafh/ai-modules --skill git_auto_reviewgit clone --depth 1 https://github.com/theafh/ai-modulesWrote 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/skills/theafh/ai-modules/git_auto_review)<a href="https://agentmods.dev/skills/theafh/ai-modules/git_auto_review"><img src="https://agentmods.dev/badge/skills/theafh/ai-modules/git_auto_review/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/theafh/ai-modules/git_auto_review"><img src="https://agentmods.dev/badge/skills/theafh/ai-modules/git_auto_review.svg" alt="Reviewed on agentmods" width="80" 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.00131 | $0.08295 |
| Opus 5.5 | $0.00052 | $0.03318 |
| Sonnet 5.5 | $0.00026 | $0.01659 |
| Haiku 4.5 | $0.00013 | $0.00830 |
Grade A, and why
git_auto_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 today.
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 — 275 lines — stays where its author put it; the contents beside it link to each section on GitHub.
git_auto_review
<git_auto_review_skill>
<when_to_activate>
Activate when the user asks for an automated review-and-fix pass over the default-branch uncommitted target this skill's <inputs> names:
- "Auto-review and fix my uncommitted changes."
- "Run the automated review loop until it is clean."
- "Keep reviewing and fixing this change until the review finds nothing."
- "Auto-fix whatever the review turns up on the working tree."
Route to git_review for manual review of any target, and for review of a branch or a pull request, whether manual or the automated review-and-fix shape. Route to a task_* sibling for task readiness work; this loop reviews a change, not a task file.
</when_to_activate>
<path_resolution>
Bundled scripts live in scripts/ next to this SKILL.md. Resolve each script's absolute path by combining the directory of this SKILL.md with scripts/<script-name> and invoke that absolute path. Resolve git_review as a same-plugin sibling skill under the skills-tree sibling form git_review/, whose first path component is that sibling's directory name under skills/ and never a repository-root plugins/<plugin>/skills/... browse path. Resolve the three helper agents auto_gate_git, auto_fixer_git, and auto_verifier_git by their published names through the harness's normal agent mechanism; when the harness exposes only file paths, those agents live in the same plugin at ../../agents/ relative to this skill directory.
</path_resolution>
- Target. The default branch's uncommitted change, reported under two lane labels: the
working-tree lane, holding the staged, the unstaged, and the untracked changes, and thelocal-commits lane, holding the local commits ahead of the upstream. Both labels are the step stringscollect_uncommittedwrites ingit_review'sscripts/collect_review_evidence.sh(working-tree lane:andlocal-commits lane:), reused as this loop'slanevocabulary. A checked-out branch target and a pull-request target are out of this skill's reach; the run declines them per<orient>. - An optional task file path that anchors scope, read by
<convergence>'s Scope anchor. and by Decisions.. - An optional round-cap override, written anywhere in the prompt as the literal phrase
round cap <N>, matched case-insensitively, where<N>is a positive integer. Absent the phrase the run proceeds with the Stop rule.'s default cap. A phrase whose integer is zero, negative, or non-numeric is not an override: the run reports that the phrase is not an override and proceeds with the default cap.
The invoking harness may also supply environment notes describing a staged helper condition. Those notes are the harness's fixture seam; apply them exactly as written and follow <agent_failure_policy> from there.
<loop_policy>
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- today First seen · 275 lines · 131 tokens per session scan A a653f5d2da82
git_auto_review is a skill published in the GitHub repository theafh/ai-modules (38 stars, last pushed today), licensed MIT. It adds 131 tokens to every session and 8,295 once invoked, about $0.0005 per session on Opus 5.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-10-29.
Other skills, from other repositories
review-implement-phase
Implements triaged review actions, commits focused fixes, and posts Done plus resolves threads. Use when the user wants only the implementation phase of the review-framework workflow.
github-pr-workflow
Prepare a GitHub pull request from a feature branch — branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments.
review-delta
Review only changes since last commit using impact analysis. Token-efficient delta review with automatic blast-radius detection.
github-contributor
A step-by-step guide for contributing code, tests, documentation, or build changes to open-source projects you do not maintain. It explains how to prepare a pull request that follows the project’s rules and is easier for maintainers to review.
hero-diff-highlight
A dark code editor reveals a red deletion then a green addition with a soft pulse. Function: PR / code-change explainer.
git-pr-workflows-git-workflow
Guide changes through code checks, testing, commits, and pull request preparation. Use when coordinating a complete Git workflow and verifying readiness for collaboration.