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/CronusL-1141/AI-companyWrote 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/cronusl-1141/ai-company/testing-bug-fixer)<a href="https://agentmods.dev/agents/cronusl-1141/ai-company/testing-bug-fixer"><img src="https://agentmods.dev/badge/agents/cronusl-1141/ai-company/testing-bug-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/cronusl-1141/ai-company/testing-bug-fixer"><img src="https://agentmods.dev/badge/agents/cronusl-1141/ai-company/testing-bug-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.00043 | $0.00220 |
| Opus 5.5 | $0.00017 | $0.00088 |
| Sonnet 5.5 | $0.00009 | $0.00044 |
| Haiku 4.5 | $0.00004 | $0.00022 |
Grade A, and why
testing-bug-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 24d 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.
What it actually says
Bug Fixer — 根因修复
- 先复现再动手，优先端到端场景。在单元测试里复现了不等于复现了——真实成因常常只在端到端层才暴露。
- 只改根因那几行：不顺手重构、不优化周边代码。diff 越小越好审，也越不容易和并行会话打架。
- 审查由派工方另行安排，不必自己再派审查者复核产出。超出任务范围的发现写进汇报的后续项，不顺手改：顺手的改动落在派工方的审查范围之外。
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.
- 24d ago Changed · -2 lines · -8 tokens per session 212aaebc2fb0
- 1mo ago Changed · -169 lines 8eec87515272
- 1mo ago First seen · 185 lines · 51 tokens per session scan A addc6f5ec2cd
testing-bug-fixer is an agent published in the GitHub repository CronusL-1141/AI-company (373 stars, last pushed 13d ago), licensed MIT. It adds 43 tokens to every session and 220 once invoked, about $0.0002 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
refactor-engineer
Behavior-preserving refactoring specialist. Hotspot repayment, characterization-test safety nets, atomic refactor-only commits. Never changes observable behavior.
debug-investigator
Bug diagnosis and fix specialist. Error analysis, root cause identification, regression test writing.
phoenix-bug-reproducer
Reproduces a reported Phoenix bug as a failing automated test. Give it the issue number, labels, the bootstrap report and the suspected area; it reports REPRODUCED with the test path and failing output, NEEDSBROWSER when the cause is confirmed but only a real browser or running server can show it, or NOTREPRODUCED…
ast-pe
A software engineering delivery agent for turning an approved design into working, maintainable software. It handles cross-module implementation, integration, testing, code review, debugging, and delivery that can be rolled back.
validator
A quality-checking agent that runs the appropriate build, test, lint, coverage, file-size, and integration checks for a project’s programming language.
tester
A test-writing agent that designs and implements unit, integration, and end-to-end tests. End-to-end tests check a complete user or system flow from start to finish.