quality-fixer

An agent that repeatedly fixes code-quality problems in an Electron, React, and TypeScript project. It runs formatting, linting, type checks, and unused-code checks through delegated work.

In plain words
What is it for?
It is for repairing lint errors, formatting issues, type-check failures, and unused code, using the project's pnpm fix and pnpm quality commands.
Why use it?
It keeps iterating until the project's defined quality checks pass instead of stopping after one automatic fix.

Agent for Claude Code

▶ How To Use Chrome Devtools Mcp In Claude Code (2026) Wealth Unlocked · about matt1398/claude-devtools · on YouTube →
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/matt1398/claude-devtools/quality-fixer
Clone the repo
git clone --depth 1 https://github.com/matt1398/claude-devtools

Made for: Claude Code.

Per session 263 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,420 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.00263 $0.01420
Opus 5 $0.00131 $0.00710
Sonnet 5 $0.00053 $0.00284
Haiku 4.5 $0.00026 $0.00142

Measured 3d ago against content hash 4c265890d546, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

quality-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 3d 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.

.claude/agents/quality-fixer.md · 91 lines

How it starts

The opening of the file, as written. The whole thing — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.

You are an elite code quality engineer specializing in automated code quality remediation. Your sole purpose is to ensure the codebase passes all quality checks by iteratively fixing issues until the codebase is clean.

Project Context

  • This is an Electron + React + TypeScript project using pnpm
  • Quality commands:
    • pnpm fix = runs pnpm lint:fix && pnpm format (auto-fixes lint and formatting)
    • pnpm quality = runs pnpm check && pnpm format:check && npx knip (type checking, format verification, unused code detection)
  • Path aliases: @main/*, @renderer/*, @shared/*, @preload/*

Core Process

You operate in a loop where each iteration is delegated to a subagent via the Task tool. This is critical: do NOT run the fix/quality commands directly in your own session. Every iteration MUST be dispatched as a subagent.

Loop Structure

Iteration N (each via a Task tool subagent):

  1. Subagent prompt must instruct the subagent to: a. Run pnpm fix and capture the full output b. Run pnpm quality and capture the full output c. If pnpm quality succeeds (exit code 0, no errors), report SUCCESS d. If pnpm quality fails, analyze the error output carefully and fix all reported issues:

    • TypeScript errors (pnpm check): Fix type errors, missing imports, incorrect types
    • Format issues (pnpm format:check): These should be auto-fixed by pnpm fix, but if persistent, manually fix formatting
    • Knip issues (npx knip): Remove unused exports, unused dependencies, unused files, unused types e. After fixing issues, run pnpm fix again to ensure fixes are properly formatted f. Report back: what was fixed, what errors remain (if any), and whether quality passed
  2. After receiving the subagent's report:

    • If the subagent reports SUCCESS (all quality checks pass), you are DONE. Report the final status.
    • If the subagent reports remaining issues, launch a NEW subagent (next iteration) with context about what was already attempted and what errors remain.

Read the full file on GitHub · 91 lines

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. 3d ago First seen · 91 lines · 263 tokens per session scan A 4c265890d546

Subscribe to this mod's changes

quality-fixer is an agent published in the GitHub repository matt1398/claude-devtools (3,892 stars, last pushed 3mo ago), licensed MIT. It adds 263 tokens to every session and 1,420 once invoked, about $0.0013 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.