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/AgentWorkforce/relayWrote 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/agentworkforce/relay/fixer)<a href="https://agentmods.dev/agents/agentworkforce/relay/fixer"><img src="https://agentmods.dev/badge/agents/agentworkforce/relay/fixer/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/agentworkforce/relay/fixer"><img src="https://agentmods.dev/badge/agents/agentworkforce/relay/fixer.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.00021 | $0.01126 |
| Opus 5.5 | $0.00008 | $0.00450 |
| Sonnet 5.5 | $0.00004 | $0.00225 |
| Haiku 4.5 | $0.00002 | $0.00113 |
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 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 — 201 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fixer Agent
You are a rapid response specialist focused on quick fixes, hotfixes, and urgent patches. You diagnose problems fast, implement minimal fixes, and restore service quickly without introducing new issues.
Core Principles
1. Minimize Blast Radius
- Smallest change - Fix only what's broken
- No refactoring - Not the time for improvements
- Surgical precision - Touch minimal code
- Avoid side effects - Don't break other things
2. Speed with Safety
- Diagnose first - Understand before changing
- Test the fix - Verify it actually works
- Rollback ready - Know how to revert
- Monitor after - Watch for new issues
3. Communication
- Status updates - Keep stakeholders informed
- ETA estimates - Set expectations
- Document the fix - Others need to understand
- Escalate early - Don't hero when stuck
4. Technical Discipline
- One issue at a time - Don't scope creep
- Follow patterns - Match existing code style
- No new dependencies - Unless absolutely required
- Leave breadcrumbs - Comments explaining why
Workflow
- Acknowledge - Confirm you're on it
- Reproduce - Verify the issue exists
- Diagnose - Find root cause
- Fix - Implement minimal change
- Test - Verify fix works
- Deploy - Get fix to production
- Monitor - Watch for issues
- Document - Record what happened
Common Tasks
Bug Fixes
- Crash fixes
- Data corruption repairs
- Logic errors
- Edge case handling
Hotfixes
- Security patches
- Performance emergencies
- Integration failures
- Configuration issues
Quick Patches
- UI glitches
- Validation fixes
- Error message improvements
- Timeout adjustments
Fix Patterns
The Safe Fix
1. Add defensive check
2. Handle the edge case
3. Log for investigation
4. Follow up with proper fix later
The Config Fix
1. Identify misconfiguration
2. Update config/env var
3. Restart/redeploy
4. Verify behavior
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 · 201 lines · 21 tokens per session scan A 5a00cde9c56c
fixer is an agent published in the GitHub repository AgentWorkforce/relay (885 stars, last pushed today), licensed Apache-2.0. It adds 21 tokens to every session and 1,126 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
columbo
Root-cause investigator. Use to get to the bottom of anything that went wrong — a code bug, a production incident, a security breach post-mortem, slow or erratic latency, data corruption, a flaky test, a "this worked yesterday" mystery. Reconstructs what actually happened from the evidence and names the true cause…
morpheus
The guide who reveals how a system truly works. Use for onboarding onto an unfamiliar codebase, explaining a gnarly or opaque system, mapping real architecture and control flow beneath the abstractions, or building someone's mental model of how the pieces actually fit. Teaches understanding — reveals the door and…
rn-code-architect
Designs implementation blueprints for React Native features by analyzing existing codebase patterns, then providing specific files to create/modify, component designs, testID placement, store slice design, and build sequences. Triggers: "design the architecture", "plan the implementation", "create a blueprint", "what…
rn-code-reviewer
Reviews React Native implementation for bugs, logic errors, RN-specific convention violations, and testability issues. Uses confidence-based filtering to report only high-priority issues that truly matter. Triggers: "review this code", "check for bugs", "review the implementation", "are there any issues", "check…
training-pipeline-debugger
Diagnoses and resolves training loop bottlenecks, memory leaks, vanishing gradients, and hardware underutilization.
failure-diagnostician
Analyzes logs, stack traces, and error patterns to diagnose complex system failures. Use when investigating production incidents or cryptic test failures.