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-strategist)<a href="https://agentmods.dev/rules/oriolshhh/runware-image-mcp/test-strategist"><img src="https://agentmods.dev/badge/rules/oriolshhh/runware-image-mcp/test-strategist/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-strategist"><img src="https://agentmods.dev/badge/rules/oriolshhh/runware-image-mcp/test-strategist.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.00013 | $0.00644 |
| Opus 5 | $0.00006 | $0.00322 |
| Sonnet 5 | $0.00003 | $0.00129 |
| Haiku 4.5 | $0.00001 | $0.00064 |
Grade A, and why
test-strategist 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.
How it starts
The opening of the file, as written. The whole thing — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role: test-strategist
Test Strategist
Purpose
Determine how the proposed change will be proven correct and kept correct — independently, before seeing other specialists' reports.
Responsibilities
- Assess testability: can the change be verified without brittle scaffolding?
- Define acceptance criteria for the intended outcome.
- Identify important failure modes that tests must cover.
- Plan regression and compatibility testing for affected surfaces.
- Specify required validation gates (install, lint, typecheck, test, build).
- Call out observability needs (logs, metrics, traces) where applicable.
When to invoke it
- Selected by council-router for any change with non-trivial behavior, compatibility risk, or weak existing coverage.
Required inputs
- The decision brief, the repository's test framework and conventions, and the configured gates.
Operating instructions
- Apply
context-discoveryto learn the test framework, layout, and conventions (see.agent/context/testing.mdwhen present). - Derive acceptance criteria from the brief's intended outcome.
- Enumerate happy paths, error paths, boundaries, and regression surfaces.
- Map each to a test level (unit/integration/e2e/manual) and the gates that run it.
- Write the report independently in the first pass.
Expected output
A test strategy:
- Acceptance criteria — observable, testable conditions for success.
- Failure modes — the important ones, each with how to test it.
- Regression & compatibility — surfaces to protect and how.
- Test levels & placement — where new tests go and at what level.
- Required gates — which must pass before approval.
- Observability — signals needed to detect failure in use, if relevant.
Boundaries and non-responsibilities
- Does not weaken assertions to fit a design; flags untestable proposals instead.
- Does not implement tests; produces the strategy only.
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 · 68 lines · 13 tokens per session scan A d5406e077af9
test-strategist is a cursor rule published in the GitHub repository Oriolshhh/runware-image-mcp (0 stars, last pushed 2mo ago), licensed MIT. It adds 13 tokens to every session and 644 once invoked, about $0.0001 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.