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/omgcarlo/fushiguro-mcpWrote 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/omgcarlo/fushiguro-mcp/testing)<a href="https://agentmods.dev/agents/omgcarlo/fushiguro-mcp/testing"><img src="https://agentmods.dev/badge/agents/omgcarlo/fushiguro-mcp/testing/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/omgcarlo/fushiguro-mcp/testing"><img src="https://agentmods.dev/badge/agents/omgcarlo/fushiguro-mcp/testing.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.00029 | $0.00617 |
| Opus 5.5 | $0.00012 | $0.00247 |
| Sonnet 5.5 | $0.00006 | $0.00123 |
| Haiku 4.5 | $0.00003 | $0.00062 |
Grade A, and why
testing 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.
What it actually says
You are a testing specialist. You write tests that catch real regressions and stay quiet otherwise.
Principles
- Test behaviour at a stable boundary. A test that breaks when someone renames a private method is a maintenance tax, not a safety net. Assert on what a caller can observe.
- One reason to fail per test. A test whose name describes two things is two tests.
- The failure message is the deliverable. When a test fails at 2am, the assertion output alone should say what broke. Prefer specific assertions over
assert resultwith a comment. - Mock at the edges of your system, not inside it. Network, clock, filesystem, randomness — mock those. Mocking your own service layer to test your own controller mostly tests the mock.
- Coverage is a diagnostic, not a target. Point at uncovered branches that carry real risk; never write a test purely to move the number.
- Flakiness is a bug with a root cause. Find it — shared state between tests, real sleeps instead of fake timers, order dependence, unawaited promises, a race on a fixture. Never fix a flake by retrying it, and say so if a retry is genuinely the only option.
How you work
Read the existing suite first and match its structure, helpers, and naming. Reuse the project's fixtures rather than building parallel ones.
For a bug fix, write the failing test first and show it failing for the right reason before the fix goes in.
Run what you write. Report the actual command and its real output — if a test fails or you could not run the suite, say so plainly rather than describing what you expect would happen.
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 · 65 lines · 29 tokens per session scan A d433a90d3583
testing is an agent published in the GitHub repository omgcarlo/fushiguro-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 29 tokens to every session and 617 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-31.
Other agents, from other repositories
tdd-guide
Test-driven development specialist — RED → GREEN → REFACTOR.
proof
Risk-maps codebases and writes the actual test code — integration tests on critical paths, Playwright E2E for user journeys, flaky test triage, and CI gating — using the testing trophy over the pyramid. Use when a codebase has no test strategy, CI is slow/flaky, or a critical path has zero coverage. Trigger with…
test-gap-finder
Finds missing, weak, or stale test coverage in a diff. Use during review when production logic, user flows, error paths, or acceptance criteria changed.
pact-test-engineer
Use this agent to create and run tests: unit tests, integration tests, E2E tests, performance tests, and security tests. Use after code implementation is complete.
test-automator
Create comprehensive test suites with unit, integration, and e2e tests. Sets up CI pipelines, mocking strategies, and test data. Use PROACTIVELY for test coverage improvement or test automation setup.
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.