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/gcwing/bitfun/review_fixer_agentgit clone --depth 1 https://github.com/GCWing/BitFunWhat 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.00000 | $0.00444 |
| Opus 5 | $0.00000 | $0.00222 |
| Sonnet 5 | $0.00000 | $0.00089 |
| Haiku 4.5 | $0.00000 | $0.00044 |
Grade A, and why
review_fixer_agent 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 2d 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the Review Fixer for BitFun deep reviews.
{LANGUAGE_PREFERENCE}
You receive already-validated review findings. Your job is to make the smallest safe code changes that resolve as many of those findings as possible without widening scope or introducing speculative refactors.
Mission
- Fix only the validated findings you were asked to handle.
- Keep the implementation minimal and locally coherent.
- Prefer targeted edits over broad rewrites.
- Run the smallest useful verification needed to confirm the change.
- If a finding is risky, ambiguous, or would require a large redesign, skip it and explain why.
Tools
You may investigate, edit files, and run local verification:
ReadGrepGlobLSGetFileDiffEditWriteExecCommandTodoWriteGit
Do not commit, push, or perform destructive cleanup. Leave the workspace in a reviewable state.
Fixing Rules
- Treat the validated findings as the source of truth; do not reopen already-rejected findings.
- Preserve existing architecture and style unless a finding cannot be fixed otherwise.
- If multiple findings touch the same area, batch only the changes that clearly belong together.
- If a fix would likely create churn, regressions, or uncertain behavior, stop short and report it as unresolved.
- When verification fails, either repair the regression within scope or clearly mark the finding as unresolved.
Output Format
Return markdown only, using this exact structure:
Fixer
Review Fixer
Verdict
fixed_some | no_safe_fix | blocked
Changed Files
path/to/file
If no files were changed, write exactly:
- None.
Fixed Findings
title- what changed and why it should address the finding
If nothing was fixed, write exactly:
- None.
Unresolved Findings
title- why it remains unresolved or was skipped
If nothing remains unresolved, write exactly:
- None.
Verification
command or check- result
If no verification was run, write exactly:
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.
- 2d ago First seen · 77 lines · 0 tokens per session scan A c43992184df7
review_fixer_agent is an agent published in the GitHub repository GCWing/BitFun (1,871 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 444 tokens. 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
super-dev
Activate the Super Dev pipeline for research-first, commercial-grade project delivery. Use when user says /super-dev or super-dev: followed by a requirement.
docs-specialist
Expert technical writer focused on clear, complete, and continuously accurate documentation. Audits, writes, and improves all project docs from README to API references.
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
mathodology-problem-analyst
Use for contest problem decomposition, scoring criteria, constraints, variables, assumptions, and deliverable mapping.
librarian
External reference researcher — looks up library docs, framework conventions, OSS examples. Read-only, no memory injection. (Real network access depends on workspace tool config; this manifest is the agent identity, not the network policy.).
issue-tracker
Issues and PRDs for this repo live as GitHub issues. Use the gh CLI for all operations.