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/rules/oriolshhh/runware-image-mcp/tester)<a href="https://agentmods.dev/rules/oriolshhh/runware-image-mcp/tester"><img src="https://agentmods.dev/badge/rules/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/rules/oriolshhh/runware-image-mcp/tester"><img src="https://agentmods.dev/badge/rules/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.00009 | $0.00450 |
| Opus 5.5 | $0.00004 | $0.00180 |
| Sonnet 5.5 | $0.00002 | $0.00090 |
| Haiku 4.5 | $0.00001 | $0.00045 |
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.
How it starts
The opening of the file, as written. The whole thing — 57 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role: tester
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.
Apply
context-discoverybefore broad scanning: use a supplied context capsule first; otherwise check context frontmatter freshness, read.agent/context/routing.md, load only relevant summaries, and verify critical claims against source.
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 · 57 lines · 9 tokens per session scan A 22f2929c2968
tester is a cursor rule published in the GitHub repository Oriolshhh/runware-image-mcp (0 stars, last pushed 3mo ago), licensed MIT. It adds 9 tokens to every session and 450 once invoked, about $0.0000 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-09-03.
Other cursor rules, from other repositories
fuzzing
Fuzzing setup and guidelines for skia-rs.
testing-and-quality
The testcomprehensive.py provides systematic testing of all 31 MCP tools.
smoke-monkey-tester
Smoke tests for core functionality and monkey/chaos tests aiming to break the system with randomized inputs. / TR: Sistemin temel fonksiyonlarını kontrol eden smoke testler ve rastgele girdilerle sistemi çökertmeyi hedefleyen monkey/chaos testleri.
testing
Testing conventions for Ion Design System using Jest and Angular Testing Library.
STAGE_S5_TEST_POINTS
A staged workflow for turning approved requirements into a complete list of test points. It checks required earlier documents and records any requirement that has no matching test point.
pre-flight-check
Mandatory fail-fast quality gate — run Typecheck, Lint, Test, and Security Audit sequentially before declaring any task done or committing code.