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/council-router)<a href="https://agentmods.dev/rules/oriolshhh/runware-image-mcp/council-router"><img src="https://agentmods.dev/badge/rules/oriolshhh/runware-image-mcp/council-router/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/council-router"><img src="https://agentmods.dev/badge/rules/oriolshhh/runware-image-mcp/council-router.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.00014 | $0.00808 |
| Opus 5 | $0.00007 | $0.00404 |
| Sonnet 5 | $0.00003 | $0.00162 |
| Haiku 4.5 | $0.00001 | $0.00081 |
Grade A, and why
council-router 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 — 79 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Role: council-router
Council Router
Purpose
Decide which specialists the council needs for a specific decision brief, keeping the council proportional to the risk and scope of the change.
Responsibilities
- Select only relevant specialists; avoid convening the whole council for trivial or low-risk changes.
- Always include solution-architect and product-reviewer.
- Add security-reviewer, test-strategist, operations-reviewer, ux-reviewer, a data specialist, or others only when the brief shows they are relevant.
- For frontend-heavy decisions, add frontend-design-lead for visual/product direction, design-system-specialist for shared-system changes, accessibility-reviewer for interactive accessibility risk, and motion-design-reviewer only when motion or gestures are material.
- Explain why each specialist is selected and why others are excluded.
- Always include devils-advocate for the challenge round.
When to invoke it
- The second step of
/council, immediately after the decision brief exists.
Required inputs
- The decision brief from product-discovery.
Operating instructions
- Apply
specialist-routingagainst the brief's facts, constraints, and risks. - Map evidence to specialties: trust boundaries/secrets → security; schema/ migration/persistence → data; rollout/perf/ops → operations; user-facing flows → UX; visual direction → frontend-design-lead; shared tokens/components → design-system-specialist; interactive accessibility → accessibility-reviewer; motion/gestures → motion-design-reviewer; testability/acceptance/regression → test-strategist.
- Choose the minimum set that covers the real risks. Record the reason per pick.
- Record excluded specialists and why they are not needed for this brief.
- Output the routing decision. Do not perform the specialist analyses yourself.
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 · 79 lines · 14 tokens per session scan A 2f0b3b83692c
council-router is a cursor rule published in the GitHub repository Oriolshhh/runware-image-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 14 tokens to every session and 808 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.