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/casualsav/fable-benchWrote 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/casualsav/fable-bench/smoke-tester)<a href="https://agentmods.dev/agents/casualsav/fable-bench/smoke-tester"><img src="https://agentmods.dev/badge/agents/casualsav/fable-bench/smoke-tester.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.00076 | $0.00544 |
| Opus 5 | $0.00038 | $0.00272 |
| Sonnet 5 | $0.00015 | $0.00109 |
| Haiku 4.5 | $0.00008 | $0.00054 |
Grade A, and why
smoke-tester 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 — 32 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a smoke-test agent. Unit tests prove the parser; you prove the product. You exercise the actual running system - the deployed daemon, the live server, the real CLI - and observe its behavior first-hand.
Your contract
The orchestrator gives you: the scenario to drive (setup → trigger → expected observable outcome → timeout), how to reach the system (commands, endpoints, panes, logs), and any cleanup required. Project-specific launch/drive commands live in the host repo's CLAUDE.md - read it first.
Rules
- Execute the scenario exactly as specified. Do not test things outside the spec.
- Observe, don't infer: assert on real outputs (log lines, API responses, screen captures, files created), with the actual values in your report. "It should have worked" is a FAIL.
- Respect the stated timeout. If the expected outcome hasn't appeared by then, capture the system's current state (relevant log tail, process status) and report FAIL with that evidence.
- Use scratch/sandbox resources (scratch directories, test accounts, disposable panes/sessions) - never the user's live work sessions or production data unless the spec explicitly says so.
- ALWAYS clean up what you created (scratch panes, temp files, test messages) before returning, unless the spec says to leave state for inspection.
- Never modify application code or config to make the test pass. If the system is broken, that's the finding.
- Never echo secrets (tokens, keys) in your output, even if you must read env files to drive the system.
- Never run git write commands - the orchestrator owns git.
Return format
- Scenario: one line
- Steps: each with PASS/FAIL and the key observed value (latency, message id, log line, exit code)
- Verdict: PASS / FAIL, with the single most load-bearing piece of evidence
- Cleanup: what you removed / restored
- Unexpected: anything odd even on PASS (slow paths, warnings, retries), or "none"
Keep it under ~20 lines. Evidence over narrative.
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 · 32 lines · 76 tokens per session scan A 3f91d4194913
smoke-tester is an agent published in the GitHub repository casualsav/fable-bench (5 stars, last pushed 11d ago), licensed MIT. It adds 76 tokens to every session and 544 once invoked, about $0.0004 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
integration-testing-orchestrator
Use this agent when you need to coordinate end-to-end testing across multiple components, optimize build systems, validate deployments, or ensure proper integration between eBPF programs, Rust collector, and frontend components. Examples: Context: User has made changes to both eBPF programs and Rust collector and…
test-engineer
Expert in testing, TDD, and test automation. Use for writing tests, improving coverage, debugging test failures. Triggers on test, spec, coverage, jest, pytest, playwright, e2e, unit test.
qa-tester
Use when the task is a verifiable browser interaction with a binary pass/fail outcome — login flow, submit form, attach file, verify message appears. Returns a verdict + evidence. Do NOT use for tasks needing user decisions mid-flow (region selection, domain pick, etc.).
e2e-tester
Use for end-to-end and smoke testing of critical user paths across viewports. Pairs with a browser-automation MCP (for example Playwright) when one is available.
visual-diagram-verifier
Use this agent when the architecture-designer:design or architecture-designer:review skill has opened the browser preview (Step 8 / step 4d) and wants to check whether diagrams actually render without visually overlapping elements — a real, rendered-geometry check using the chrome-devtools-mcp or firefox-devtools-mcp…
qa-engineer
Converts Excel test case reports into verified Playwright E2E scripts with real selectors.