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/tradeoff-analysis)<a href="https://agentmods.dev/rules/oriolshhh/runware-image-mcp/tradeoff-analysis"><img src="https://agentmods.dev/badge/rules/oriolshhh/runware-image-mcp/tradeoff-analysis/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/tradeoff-analysis"><img src="https://agentmods.dev/badge/rules/oriolshhh/runware-image-mcp/tradeoff-analysis.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.00428 |
| Opus 5 | $0.00005 | $0.00214 |
| Sonnet 5 | $0.00002 | $0.00086 |
| Haiku 4.5 | $0.00001 | $0.00043 |
Grade A, and why
tradeoff-analysis 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: tradeoff-analysis
Tradeoff Analysis
Purpose
Make a recommendation defensible by comparing real alternatives against stated criteria instead of asserting a single option.
When to use it
- Whenever a specialist or the chair must choose between approaches.
- Before recommending any non-trivial design or product direction.
Instructions
- State the decision and the criteria up front (e.g., correctness, user value, complexity, risk, reversibility, effort, performance). Note relative weight.
- Identify at least two viable options, including a "do less / reuse / defer" option. Avoid strawmen.
- Score each option against each criterion, citing evidence for the score.
- Make the reversibility of each option explicit; prefer reversible options under uncertainty.
- State the recommendation, the margin by which it wins, and what evidence would change it.
Output format
A comparison: criteria (with weights), options, a per-criterion assessment with citations, the recommendation with its winning margin, and the conditions that would flip the decision.
Anti-patterns
- Presenting one option as if no alternative exists.
- Strawman alternatives that exist only to be rejected.
- Hiding the criteria, or changing them to fit a preferred answer.
- Ignoring reversibility and effort.
Verification checklist
- Criteria are stated before options are scored.
- At least two genuine options are compared with evidence.
- Reversibility and effort are considered.
- The conditions that would change the conclusion are stated.
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 · 50 lines · 9 tokens per session scan A 25ba6add97ba
tradeoff-analysis is a cursor rule published in the GitHub repository Oriolshhh/runware-image-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 9 tokens to every session and 428 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
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.