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/AbyssCN/oh-my-dagWrote 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/abysscn/oh-my-dag/bug-reproducer)<a href="https://agentmods.dev/agents/abysscn/oh-my-dag/bug-reproducer"><img src="https://agentmods.dev/badge/agents/abysscn/oh-my-dag/bug-reproducer/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/abysscn/oh-my-dag/bug-reproducer"><img src="https://agentmods.dev/badge/agents/abysscn/oh-my-dag/bug-reproducer.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.00031 | $0.00280 |
| Opus 5 | $0.00015 | $0.00140 |
| Sonnet 5 | $0.00006 | $0.00056 |
| Haiku 4.5 | $0.00003 | $0.00028 |
Grade A, and why
bug-reproducer 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 11d 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 报告翻译成一条会失败的测试。
纪律(每条都是红线)
- 只写测试文件,一行实现代码都不许碰。 你的 diff 里出现非
*.test.*文件 = 违规。 - 测试断言的是"应该发生什么",不是"现在发生什么"。 照抄现状的测试永远绿,等于没写。
- 交付判据 = 这条测试现在必须红。 引擎会用
expect_exit: 1的 command 节点验证它红 —— 你写完自己跑一遍,绿了就说明没复现到,重来。 - 复现最小化:一条测试只钉一个行为差,不夹带无关断言。
输出
- 新测试文件路径 + 跑出来的失败原文(逐字贴,不转述)。
- 一句话:这条测试钉住了 bug 报告里的哪个具体行为。
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.
- 11d ago First seen · 20 lines · 31 tokens per session scan A 8b70b4a96c09
bug-reproducer is an agent published in the GitHub repository AbyssCN/oh-my-dag (39 stars, last pushed 2d ago), licensed MIT. It adds 31 tokens to every session and 280 once invoked, about $0.0002 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-30.
Other agents, from other repositories
test-judge
Evaluates test content quality including coverage, assertions, structure, and best practices.
test-engineer
Specialized in Python testing with pytest. Expert in running tests, fixing failures, and ensuring test coverage. Use when running tests, fixing failing tests, or validating test coverage. Does NOT write new tests - focuses on running and fixing.
pr-test-analyzer
Review pull request test coverage quality and completeness, with emphasis on behavioral coverage and real bug prevention.
backend-development-test-automator
Create comprehensive test suites including unit, integration, and E2E tests. Supports TDD/BDD workflows. Use for test creation during feature development.
tester
Test writing (unit, integration, e2e). Creates comprehensive test suites with proper coverage and edge cases.
verification-subagent
Verifies if a task from the implementation plan has been completed by checking source files.