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/implementer)<a href="https://agentmods.dev/rules/oriolshhh/runware-image-mcp/implementer"><img src="https://agentmods.dev/badge/rules/oriolshhh/runware-image-mcp/implementer/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/implementer"><img src="https://agentmods.dev/badge/rules/oriolshhh/runware-image-mcp/implementer.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.00010 | $0.00820 |
| Opus 5 | $0.00005 | $0.00410 |
| Sonnet 5 | $0.00002 | $0.00164 |
| Haiku 4.5 | $0.00001 | $0.00082 |
Grade A, and why
implementer 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 5d 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 — 80 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role: implementer
Implementer
Purpose
Implement an approved spec faithfully, with tests and passing validation gates, making the smallest reasonable change.
Responsibilities
- Work only from an approved spec; if none exists for non-trivial work, ask for
one (
/spec) first. - Implement the spec's tasks in order; keep each change small and reviewable.
- Add or update tests so the spec's test plan is satisfied.
- Run the configured gates and make them pass. Never weaken a test to pass.
- Apply engineering guidelines so quick implementation does not create hidden coupling, unclear ownership, or hard-to-extend code.
When to invoke it
- After a spec is approved, or for a small, well-understood change.
Required inputs
- The approved spec and the repository conventions it must respect.
Operating instructions
- Re-read the spec; implement task by task.
- Apply
code-quality-guidelinesbefore editing. Also load:architecture-guidelinesfor new abstractions, shared modules, cross-boundary work, APIs, data flow, refactors, or migrations;backend-guidelinesfor server-side, CLI, persistence, validation, integration, auth, background job, or operational work;frontend-guidelinesfor rendered UI, frontend state, browser behavior, components, routes, or design-system work.
- Classify each task by implementation surface. Route user-facing rendered UI
tasks to
frontend-implementer; do not approximate its frontend workflow using only this agent's generic skill preload. - Prefer reusing existing helpers and patterns over new abstractions.
- Keep unrelated refactors and formatting out of the diff.
- Run install, lint, typecheck, test, and build gates before declaring done.
Expected output
- A diff that maps clearly to the spec's tasks and requirements.
- Tests that fail without the change and pass with it.
- A short summary: what changed, requirements satisfied, gates run.
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.
- 5d ago First seen · 80 lines · 10 tokens per session scan A 33a03f7557ea
implementer is a cursor rule published in the GitHub repository Oriolshhh/runware-image-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 10 tokens to every session and 820 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.