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/test-design)<a href="https://agentmods.dev/rules/oriolshhh/runware-image-mcp/test-design"><img src="https://agentmods.dev/badge/rules/oriolshhh/runware-image-mcp/test-design/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/test-design"><img src="https://agentmods.dev/badge/rules/oriolshhh/runware-image-mcp/test-design.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.00007 | $0.00363 |
| Opus 5 | $0.00003 | $0.00181 |
| Sonnet 5 | $0.00001 | $0.00073 |
| Haiku 4.5 | $0.00001 | $0.00036 |
Grade A, and why
test-design 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 6d 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
Skill: test-design
Test Design
Purpose
Create tests that document expected behavior, catch regressions, and remain stable as implementation details change.
When to use it
- Whenever you add or change behavior.
- When a bug is found (write a failing test first, then fix).
Instructions
- Derive cases from requirements and edge cases, not from the implementation.
- Cover happy paths, error paths, boundaries, and empty/large inputs.
- Assert observable behavior and meaningful content.
- Keep tests deterministic: no real time, network, or machine-specific state.
- Name each test after the behavior it verifies.
Output format
Test files with clear names and assertions, plus a short mapping from tests to requirements.
Anti-patterns
- Asserting only existence ("file was created") without checking content.
- Coupling tests to internal details that should be free to change.
- Weakening a test to make a broken implementation pass.
Verification checklist
- Include positive, negative, boundary, malformed, empty, and large-input cases that are relevant to the requirement.
- Prove the regression test detects the old defect when practical.
- Keep fixtures minimal and isolate time, randomness, network, and filesystem state behind deterministic controls.
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.
- 6d ago First seen · 45 lines · 7 tokens per session scan A 12f70244a287
test-design is a cursor rule published in the GitHub repository Oriolshhh/runware-image-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 7 tokens to every session and 363 once invoked, about $0.0000 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-09-03.
Other cursor rules, from other repositories
20-testing-generated-and-structure
Testing expectations, generated-file boundaries, and CLI structure contract.
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.
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.
testing
Testing conventions for Ion Design System using Jest and Angular Testing Library.