fixer

A focused code-fixing agent handles one failing test or type or compile error at a time. It investigates the cause, makes a small change, and checks the result again.

In plain words
What is it for?
Use it to fix a specific red test, type-checking error, or compilation error while preserving the test's strength.
Why use it?
It keeps debugging focused and avoids unrelated edits or changes that merely hide the failure. It also reports when a genuine fix cannot be found.

Agent

Install

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.

agentmods
npx agentmods add agents/localplugins/plugins/fixer
Clone the repo
git clone --depth 1 https://github.com/localplugins/plugins
Per session 42 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 277 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00042 $0.00277
Opus 5 $0.00021 $0.00138
Sonnet 5 $0.00008 $0.00055
Haiku 4.5 $0.00004 $0.00028

Measured yesterday against content hash 727daa5c0156, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

fixer 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 yesterday.

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.

green-keeper/agents/fixer.md · 17 lines

What it actually says

You fix ONE red item (a failing test or a type/compile error) at a time, correctly and minimally, following the anti-fake-green skill.

Process

  1. Read the failure output and the code involved. Form a hypothesis about the real cause.
  2. Make the smallest change to production code (or the genuinely-wrong test) that fixes the root cause. Do not touch unrelated code. Never edit vendored/generated files.
  3. Obey anti-fake-green: no skipping/weakening tests, no silencing errors, no any, no coverage padding.
  4. Re-run the relevant test and typecheck (commands from .green-keeper/config.json). If still red, iterate; if you cannot find a genuine fix, STOP and report exactly what's blocking — do not fake it.
  5. Keep the diff minimal and explain the root cause in one or two sentences.

Report: the root cause, the minimal change, and the re-run result (pass/still-red). Never access the network.

Changes

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.

  1. yesterday First seen · 17 lines · 42 tokens per session scan A 727daa5c0156

Subscribe to this mod's changes

fixer is an agent published in the GitHub repository localplugins/plugins (5 stars, last pushed 1mo ago), licensed MIT. It adds 42 tokens to every session and 277 once invoked, about $0.0002 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-31.

Related

Other agents, from other repositories

implementation-agent

Strict implementation agent that executes coding tasks following requirements exactly without improvisation, asking for clarification when needed.

NikiforovAll/claude-code-rules · 22 tokens

bash-pro

Production-quality bash scripting with shellcheck compliance, robust error handling, and beautiful terminal UX. Use for shell scripts, CLI tools, and automation.

sgaunet/claude-plugins · 32 tokens

database-specialist

Multi-engine database expert (MySQL, MongoDB, Redis, SQLite, SQL Server) for schema design, query optimization, and performance tuning. Use for general or cross-engine database design and scaling issues; defer PostgreSQL-specific work to postgresql-specialist.

sgaunet/claude-plugins · 56 tokens

aws-specialist

AWS cloud architecture expert for infrastructure design, cost optimization, and Well-Architected Framework. Use PROACTIVELY for AWS-specific tasks.

sgaunet/claude-plugins · 32 tokens

qg-implementation

Use this agent to validate Implementation phase output against domain-specific quality criteria. Most comprehensive QG — covers hallucination detection, contract conformance, file size, test distribution, V-Model levels, AC coverage, design spec compliance, and execution results. Returns PASS/WARN/FAIL verdict.…

baodq97/open-plugin · 163 tokens

prototype-architect

Use this agent to produce feature specifications, user flows, constraints, success criteria, and scope boundaries from the selected solution direction. Invoked after the Prototype constraints conversation is complete. Context: Prototype constraints gathered, need feature specification. user: "Constraints are captured.…

baodq97/open-plugin · 114 tokens