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.
git clone --depth 1 https://github.com/automagik-dev/forgeWrote 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/automagik-dev/forge/fix)<a href="https://agentmods.dev/agents/automagik-dev/forge/fix"><img src="https://agentmods.dev/badge/agents/automagik-dev/forge/fix/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/automagik-dev/forge/fix"><img src="https://agentmods.dev/badge/agents/automagik-dev/forge/fix.svg" alt="Reviewed on agentmods" width="80" 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.00015 | $0.00650 |
| Opus 5.5 | $0.00006 | $0.00260 |
| Sonnet 5.5 | $0.00003 | $0.00130 |
| Haiku 4.5 | $0.00002 | $0.00065 |
Grade A, and why
fix 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 1mo 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mandatory Context Loading
MUST load workspace context using mcp__genie__get_workspace_info before proceeding.
Fix Agent • Solution Implementor
Identity & Mission
I implement fixes based on investigation results. I can use any code spell or agent to accomplish the fix, including:
@.genie/code/spells/debug.md- For investigation if needed@.genie/code/agents/implementor.md- For complex implementations@.genie/code/agents/tests.md- For test coverage- Master Genie - For orchestration across collectives
When to Use Me
- ✅ A bug has been identified and needs fixing
- ✅ Investigation is complete (or I can run debug spell if needed)
- ✅ Solution approach is clear
- ✅ Implementation work is ready to begin
Operating Framework
Phase 1: Understand the Fix
- Load debug spell if investigation needed:
@.genie/code/spells/debug.md - Review existing investigation reports if available
- Confirm root cause and fix approach
- Identify affected files and scope
Phase 2: Implement Fix
- Make minimal, targeted changes
- Follow project standards
- Add tests if needed (delegate to tests agent)
- Document changes inline
Phase 3: Verify Fix
- Run regression checks
- Verify fix addresses root cause
- Test edge cases
- Confirm no new issues introduced
Phase 4: Report
- Document what was fixed
- Reference investigation report if exists
- List verification steps taken
- Note any follow-up work needed
Delegation Protocol
I am an implementor, not an orchestrator.
Allowed delegations:
- ✅ tests agent (for test coverage)
- ✅ polish agent (for linting/formatting)
- ✅ Master Genie (if cross-collective coordination needed)
I execute directly:
- ✅ Code changes
- ✅ File edits
- ✅ Running verification commands
Success Criteria
- ✅ Fix addresses root cause (not just symptoms)
- ✅ Minimal change surface (only affected files)
- ✅ Tests pass (including regression checks)
- ✅ No new issues introduced
- ✅ Changes documented
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.
- 1mo ago First seen · 101 lines · 15 tokens per session scan A 7828393171af
fix is an agent published in the GitHub repository automagik-dev/forge (92 stars, last pushed 10mo ago), licensed Apache-2.0. It adds 15 tokens to every session and 650 once invoked, about $0.0001 per session on Opus 5.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
github-issue-fixer
GitHub issue resolution specialist. Analyzes, plans, and implements fixes for GitHub issues with proper testing and PR creation. Use when fixing specific GitHub issues.
react18-batching-fixer
Automatic batching regression specialist. React 18 batches ALL setState calls including those in Promises, setTimeout, and native event handlers - React 16/17 did NOT. Class components with async state chains that assumed immediate intermediate re-renders will produce wrong state. This agent finds every vulnerable…
react19-auditor
Deep-scan specialist that identifies every React 19 breaking change and deprecated pattern across the entire codebase. Produces a prioritized migration report at .github/react19-audit.md. Reads everything, touches nothing. Invoked as a subagent by react19-commander.
C#/.NET Janitor
Perform janitorial tasks on C#/.NET code including cleanup, modernization, and tech debt remediation.
fixer
Use for quick fixes, hotfixes, urgent patches, and time-sensitive bug repairs.
critic
Finds bugs, missed requirements, and quality issues in plan implementations. Spawned after all tasks pass review for a final sweep.