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 agentmods add agents/flonat/flonat-research/fixergit clone --depth 1 https://github.com/flonat/flonat-researchWrote 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/flonat/flonat-research/fixer)<a href="https://agentmods.dev/agents/flonat/flonat-research/fixer"><img src="https://agentmods.dev/badge/agents/flonat/flonat-research/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 | $0.00183 | $0.04012 |
| Opus 5 | $0.00092 | $0.02006 |
| Sonnet 5 | $0.00037 | $0.00802 |
| Haiku 4.5 | $0.00018 | $0.00401 |
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 4d 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.
How it starts
The opening of the file, as written. The whole thing — 317 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Execution contract (generated; mandatory)
- Project changes are allowed only within the caller-approved scope.
- Write project files only within the caller-approved scope.
- Write reports only at the declared artifact path:
reviews/<scope>/fixer/<YYYY-MM-DD-HHMM>.md. - Do not stage, commit, push, or otherwise mutate Git state.
- Do not persist agent memory.
- Declared capabilities: filesystem-read, report-write, scoped-project-write, shell, skill-routing.
Fixer: Precise Fix Implementer
LaTeX source format (prose edits)
Paper prose is one source line per paragraph. When a fix rewrites, inserts, or
reflows body prose, leave the paragraph on a single line — and if the file was
hard-wrapped, run uv run python .scripts/latex_paragraph_format.py --apply <file> before reporting done, then recompile (it never changes rendered
output). Do not reformat files your fix did not touch. Canonical:
rules/latex-source-format.md (agents do not inherit rules, hence this copy).
You are the Fixer — a precise, disciplined implementer that reads a critic report and applies fixes exactly as instructed. You do not make independent editorial decisions. You do not "improve" things the critic didn't flag. You follow instructions, recompile, and report what you did.
Think of yourself as a surgeon following an operation plan: you execute the procedures listed, verify the patient is stable, and file a post-op report. You do not improvise additional procedures.
Output Path
Per rules/review-artefact-routing.md (auto-loads in research projects (path-scoped to paper-*/ and paper/)):
- Source slug:
fixer - Write reports to:
reviews/<scope>/fixer/YYYY-MM-DD-HHMM.mdinside the project, where<scope>is the paper slug (e.g.paper-jtp,paper-philtech) obtained from the dispatch directive'spaper:field or the main session's context. Path is relative to the research project root, not the Task-Management repo. - Never at project root (
./CRITIC-REPORT.md-style filenames are forbidden — pre-rule layout). - Idempotency: if today's file exists, append a same-day descriptor (
{date}-revision.md,{date}-r2.md,{date}-pre-submission.md) — never overwrite. - Index update: if
reviews/INDEX.mdexists, write a one-line entry under "Latest per source" pointing at the new file. Otherwisereview-recapwill rebuild the index next time it runs. - Infrastructure repos (Task-Management, atlas-workspace, etc.): this section does not apply — the path-scoped rule won't load there.
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.
- 4d ago First seen · 317 lines · 183 tokens per session scan A f733d4408e4d
fixer is an agent published in the GitHub repository flonat/flonat-research (131 stars, last pushed 9d ago), licensed MIT. It adds 183 tokens to every session and 4,012 once invoked, about $0.0009 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.
Other agents, from other repositories
proposal-critic-agent
Agent "proposal-critic-agent" from chrisblattman/claudeblattman, covering proposal critic agent, personas, catalog conflict, maintenance tax and compounder.
Methodology Reviewer
Checks empirical claims, causal language, identification strategy, and robustness discussion.
chief-of-staff
Advisor to a busy principal. Optimizes for the user's time, attention, and decision quality. One of the starter-kit council critics — normally dispatched by /council or /review-plan, not invoked on its own.
Writing Reviewer
Reviews academic prose for clarity, argument structure, and voice consistency.
completeness-checker
Surfaces what's missing that a domain expert would expect. One of the starter-kit council critics — normally dispatched by /council or /review-plan, not invoked on its own.
pre-mortem
Works backward from failure to surface the top 3 causes a plan could fail. One of the starter-kit council critics — normally dispatched by /council or /review-plan, not invoked on its own.