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/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/agents/theafh/ai-modules/auto_fixer_git)<a href="https://agentmods.dev/agents/theafh/ai-modules/auto_fixer_git"><img src="https://agentmods.dev/badge/agents/theafh/ai-modules/auto_fixer_git/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/agents/theafh/ai-modules/auto_fixer_git"><img src="https://agentmods.dev/badge/agents/theafh/ai-modules/auto_fixer_git.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.00127 | $0.01318 |
| Opus 5.5 | $0.00051 | $0.00527 |
| Sonnet 5.5 | $0.00025 | $0.00264 |
| Haiku 4.5 | $0.00013 | $0.00132 |
Grade A, and why
auto_fixer_git 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Auto Fixer Git
- The target: the default branch's uncommitted change under the two lane labels the
git_auto_reviewskill's<lane_classification>names, so each fix anchors at the whole-file working-tree lines its finding'slocationnames. - The round's approved finding set: one block per finding, each carrying the gate
id,heading,label,location, andFixfrom the round's gate return, as the verifier approved it. - The run's relay directory, including
ledger.txt, which holds the run's regression ledger under the skill's Regression ledger. rule. - The anchoring task file path when the run was given one, read only to confirm a fix's intent boundary.
- On a retry, the named failure that authorizes it: the failing
ledger.txtline for a Regression ledger. retry, or the unmapped hunks from the round'sround-r<round>.diff.txtfor an<audit_delta>retry.
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 · 65 lines · 127 tokens per session scan A b5d756f04799
auto_fixer_git is an agent published in the GitHub repository theafh/ai-modules (38 stars, last pushed today), licensed MIT. It adds 127 tokens to every session and 1,318 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 agents, from other repositories
pr-test-analyzer
Review pull request test coverage quality and completeness, with emphasis on behavioral coverage and real bug prevention.
testing-reviewer
Reviews test code for Elixir best practices - ExUnit patterns, Mox usage, LiveView testing, factory patterns. Use proactively after writing tests or during code review.
ai-hygiene-auditor
Audit codebases for AI-generation warning signs: vibe coding patterns, agent psychosis indicators, slop artifacts, and Tab-completion bloat. Specialized complement to bloat-auditor.
test-gap-finder
Finds missing, weak, or stale test coverage in a diff. Use during review when production logic, user flows, error paths, or acceptance criteria changed.
openinference-js-reviewer
Read-only reviewer for OpenInference TypeScript changes - instrumentors, core and semantic conventions under js/packages/. Give it the changed paths and what the change is meant to do; it reports verified findings with file:line evidence and a severity. Spawn it once per review round.
openinference-python-reviewer
Read-only reviewer for OpenInference Python changes - instrumentors under python/instrumentation/, the openinference-instrumentation core and the semantic conventions. Give it the changed paths under python/ and what the change is meant to do; it reports verified findings with file:line evidence and a severity. Spawn…