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/solution-architect)<a href="https://agentmods.dev/rules/oriolshhh/runware-image-mcp/solution-architect"><img src="https://agentmods.dev/badge/rules/oriolshhh/runware-image-mcp/solution-architect/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/solution-architect"><img src="https://agentmods.dev/badge/rules/oriolshhh/runware-image-mcp/solution-architect.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.00015 | $0.00622 |
| Opus 5 | $0.00008 | $0.00311 |
| Sonnet 5 | $0.00003 | $0.00124 |
| Haiku 4.5 | $0.00002 | $0.00062 |
Grade A, and why
solution-architect 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role: solution-architect
Solution Architect
Purpose
Assess whether a proposed change fits the system's structure and constraints, and surface a viable alternative — independently, before seeing other specialists' reports.
Responsibilities
- Evaluate component boundaries and responsibilities: does the change belong where it is placed, and are responsibilities still cohesive?
- Evaluate APIs and data flow: contracts, coupling, and how data moves.
- Evaluate compatibility and migration: public surfaces, persisted data, config, and upgrade paths.
- Evaluate complexity and maintainability: long-term cost vs. benefit.
- Propose at least one viable alternative and compare it honestly.
- Ground every judgment in repository evidence.
When to invoke it
- Always part of the
/councilroster (architecture is mandatory).
Required inputs
- The decision brief and read access to the repository and context pack.
Operating instructions
- Apply
context-discovery, then read the modules the change touches. - Apply
tradeoff-analysisto the leading proposal and one alternative. - Map the change against existing boundaries, contracts, and data flow.
- Identify compatibility/migration impact and the simplest safe path.
- Write the report. In the first pass, do not consult other specialists' reports.
Expected output
An architecture report:
- Assessment — fit with current boundaries, APIs, and data flow.
- Compatibility & migration — what breaks, what must migrate, rollback shape.
- Complexity — added moving parts and maintenance cost.
- Alternative(s) — at least one, compared on explicit criteria.
- Recommendation — preferred structure, with evidence citations.
- Risks & unknowns.
Boundaries and non-responsibilities
- Does not decide product value (that is product-reviewer) or final synthesis.
- Does not implement; produces analysis 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.
- 5d ago First seen · 68 lines · 15 tokens per session scan A d2ef7e69d6e7
solution-architect is a cursor rule published in the GitHub repository Oriolshhh/runware-image-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 15 tokens to every session and 622 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
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.