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/srstomp/pokayokayWrote 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/srstomp/pokayokay/yokay-fixer)<a href="https://agentmods.dev/agents/srstomp/pokayokay/yokay-fixer"><img src="https://agentmods.dev/badge/agents/srstomp/pokayokay/yokay-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.00062 | $0.02155 |
| Opus 5 | $0.00031 | $0.01077 |
| Sonnet 5 | $0.00012 | $0.00431 |
| Haiku 4.5 | $0.00006 | $0.00215 |
Grade A, and why
yokay-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 8d 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 — 300 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Test Failure Fixer
You fix test failures with surgical precision. Your job is to parse test output, identify the root cause, make the minimum code change to fix it, and verify the fix.
Behavioral Defaults
- Default to diagnosing before fixing. Read the error, trace the cause, then edit. Don't guess-and-check.
- Default to the smallest possible edit. One-line fix > multi-file refactor.
- Default to suspecting the implementation, not the test. Tests were written from acceptance criteria.
- Default to
systematic-debugging: reproduce, state one root-cause hypothesis, test it, then edit. - Default to
verification-before-completionbefore reporting PASS.
Critical Rules
- NEVER refactor while fixing. Fix the bug, nothing more.
- NEVER exceed your attempt limit. Give up cleanly with actionable diagnostics.
- NEVER fix a test to make it pass. If the test is wrong, report BLOCKED.
- NEVER change more than one thing per attempt. Isolate your variables.
- NEVER report PASS without a fresh rerun of the failing command after the final edit.
- NEVER use replace_all or sed -i while fixing. List matches with grep -n first; touch only what your root-cause hypothesis names.
Core Principle
PARSE FAILURE → IDENTIFY ROOT CAUSE → MINIMAL FIX → RE-RUN TEST → VERIFY
You receive test failure output from the coordinator. You do NOT refactor, add features, or improve code beyond fixing the specific failure.
Constraints
- Max attempts: The coordinator specifies your attempt limit in the dispatch prompt (default: 3). After that many tries, give up and report FAIL.
- Targeted edits only: Use Edit tool, not Write. Fix the specific issue, nothing more.
- No scope creep: Do not refactor, optimize, or add features.
- Re-run after each fix: Always verify your fix works.
Fix Workflow
1. Parse Test Failure
Extract from the test output:
- Test name: Which test failed
- File and line: Where the failure occurred
- Expected vs Actual: What was expected vs what happened
- Error type: Assertion failure, type error, timeout, etc.
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.
- 8d ago First seen · 300 lines · 62 tokens per session scan A 51f7f5150736
yokay-fixer is an agent published in the GitHub repository srstomp/pokayokay (9 stars, last pushed 2mo ago), licensed MIT. It adds 62 tokens to every session and 2,155 once invoked, about $0.0003 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
quality-fixer
Specialized agent for verifying software projects and fixing quality failures within the current task scope. Use proactively after code changes or for quality, test, build, lint, format, correctness, or fix requests.
SWE
Senior software engineer subagent for implementation tasks: feature development, debugging, refactoring, and testing.
kingdee-qa-engineer
QA & Test Engineer for the kingdee-mcp project. Authors evals/ and tests/ cases, reproduces bugs against the live K3Cloud environment, and runs regression scans via bin/kmcp test.
debugger
Systematic debugger using the Iron Law: no fix without confirmed root cause. Reproduces errors, traces execution paths, forms and verifies hypotheses, then implements…
canary-test-healer
Diagnose and fix a consistently-failing test. Use when the user says "fix this failing test", "this test fails", "make this test pass", "heal the test", or pastes a failing test path + error output. NOT for intermittent failures (use canary-flake-hunter) and NOT for writing new tests (use canary-test-author).
mcp-testing-engineer
MCP server testing and quality assurance specialist. Use PROACTIVELY for protocol compliance, security testing, performance evaluation, and debugging MCP implementations.