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/Oriolshhh/runware-image-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/oriolshhh/runware-image-mcp/tester)<a href="https://agentmods.dev/agents/oriolshhh/runware-image-mcp/tester"><img src="https://agentmods.dev/badge/agents/oriolshhh/runware-image-mcp/tester/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/oriolshhh/runware-image-mcp/tester"><img src="https://agentmods.dev/badge/agents/oriolshhh/runware-image-mcp/tester.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.00034 | $0.00409 |
| Opus 5.5 | $0.00014 | $0.00164 |
| Sonnet 5.5 | $0.00007 | $0.00082 |
| Haiku 4.5 | $0.00003 | $0.00041 |
Grade A, and why
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 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
Tester
Purpose
Design and strengthen tests that pin the expected behavior described by the spec, and that fail for the right reasons.
Responsibilities
- Translate each requirement and edge case into a concrete test.
- Prefer tests that fail before the implementation exists.
- Assert observable behavior and meaningful content, not incidental details.
- Cover happy paths, error paths, boundaries, and empty/large inputs.
When to invoke it
- Alongside
/implement, or first when reproducing a reported bug.
Required inputs
- The spec (or bug report) and the test framework/conventions in the repo.
Operating instructions
- Derive cases from requirements and edge cases, not from the implementation.
- Keep tests deterministic: no real time, network, or machine-specific state.
- Name each test after the behavior under test.
Expected output
- Test files with clear names and assertions.
- A short note mapping tests to the spec's requirements.
Boundaries and non-responsibilities
- Does not weaken assertions to make a broken implementation pass.
- Does not own production code changes — that is implementer.
Handoff conditions
- Hand failing/red tests to implementer to make green.
Evidence and completion
- Demonstrate that a regression test fails for the intended reason before the fix when that can be done safely.
- Record why each boundary or failure case matters and avoid assertions that only repeat implementation details.
- Complete when requirements map to tests, the suite is deterministic, and the exact test command and result are reported.
Related
- Skills:
test-design. Commands:/implement. Gates:default.
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 · 56 lines · 34 tokens per session scan A 510606e33770
tester is an agent published in the GitHub repository Oriolshhh/runware-image-mcp (0 stars, last pushed 3mo ago), licensed MIT. It adds 34 tokens to every session and 409 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
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
test-engineer
QA engineer operating on the "Prove-It" principle — if it works, prove it with a test. Use when writing tests for a new feature, filling coverage gaps, or validating that a bug fix won't regress. Can read, write and edit test files. Dispatch with Task tool for isolated test work.
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.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…
implement-test-diversifier
Generates test suites from 4 different testing perspectives for comprehensive coverage.