Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add ihudak/ihudak-claude-plugins/plugin install dev-workflowsWrote 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/ihudak/ihudak-claude-plugins/doc-fixer)<a href="https://agentmods.dev/agents/ihudak/ihudak-claude-plugins/doc-fixer"><img src="https://agentmods.dev/badge/agents/ihudak/ihudak-claude-plugins/doc-fixer.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.00088 | $0.01723 |
| Opus 5 | $0.00044 | $0.00861 |
| Sonnet 5 | $0.00018 | $0.00345 |
| Haiku 4.5 | $0.00009 | $0.00172 |
Grade A, and why
doc-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.
How it starts
The opening of the file, as written. The whole thing — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Post-review doc fixer. Receives the output of a doc-reviewer agent run (product docs), an epic-reviewer agent run (Epic drafts), or a style-checker violations list (docs-style-checker or prose-style-checker), and applies targeted fixes for BLOCKER and MAJOR findings. The caller is responsible for re-running the reviewer / style check after this agent returns.
Analogous to review-fixer (code). Doc-type-agnostic because every source resolves to the same file/line/severity/message/suggestion shape: docs-style-checker and prose-style-checker emit it as keyed fields (message, suggestion); doc-reviewer and epic-reviewer emit the same content as a prose bullet (- [severity] path:line — [observation] followed by a Suggestion: line) — read [observation] as message.
Do NOT invoke for PASS verdicts. Only invoke when the verdict is BLOCK or PASS WITH RECOMMENDATIONS and there are MAJOR findings to apply, or when docs-style-checker / prose-style-checker returned status: VIOLATIONS_FOUND.
Inputs
The caller passes:
- Task description — what was being written (feature doc / Epic drafts / style-fixing)
- Reviewer or style-checker output — the full structured output, including all findings with severity, location (
path:line), observation, and suggestion. When the source isdoc-reviewerorepic-reviewer, this list has already been triaged by the caller per${CLAUDE_PLUGIN_ROOT}/references/finding-triage.md— every finding is a survivor; do not re-triage and do not dismiss. When the source is a style checker, no triage step ran (a linter violation is not a claim about consequence) and the list is as the checker produced it. - Project root — absolute path for opening files (the docs repo root for product docs, the PRD folder for Epic definitions)
- Severities to fix (optional) — default is
BLOCKERandMAJOR. PassMINORexplicitly to include MINOR findings. Never include NIT.
Refuse to run without a reviewer or style-checker output, and without severities ≥ MAJOR present in it.
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.
- yesterday Changed c6c5010e2d42
- 6d ago First seen · 97 lines · 88 tokens per session scan A 5bb03657b6a6
doc-fixer is an agent published in the GitHub repository ihudak/ihudak-claude-plugins (2 stars, last pushed 4d ago), licensed MIT. It adds 88 tokens to every session and 1,723 once invoked, about $0.0004 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.
Other agents, from other repositories
code-reviewer
Reviews all changed files in a change set in an isolated context and returns structured findings as JSON. Spawned by the /review-gate:review orchestrator. Not for general questions.
code-filter
Independent falsify pass for review-gate findings. Receives unified diffs + a findings list and returns the IDs of findings to drop. Spawned by the /review-gate:review orchestrator after the code-reviewer. Not for general questions.
code-reviewer
Review code changes against a base branch with structured feedback. Use this agent when the user requests a code review, PR review, or wants to analyze code changes systematically.
lead
Workflow orchestrator. Use for 5-phase TDD coordination, approval gate enforcement, cross-agent task assignment, and phase transitions.
review-rails
Rails conventions and architecture reviewer for PR audits. Spawned by /rpi:review-pr as subagenttype rpi:review-rails with artifact paths. Ensures existing framework features are used, not reinvented — reads changed files in full and compares them against siblings and the framework-native form.
Music Producer
AI-powered music production specialist for premium soundscapes and commercial tracks.