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/decision-synthesis)<a href="https://agentmods.dev/rules/oriolshhh/runware-image-mcp/decision-synthesis"><img src="https://agentmods.dev/badge/rules/oriolshhh/runware-image-mcp/decision-synthesis.svg" alt="Measured on agentmods" 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.00490 |
| Opus 5 | $0.00007 | $0.00245 |
| Sonnet 5 | $0.00003 | $0.00098 |
| Haiku 4.5 | $0.00001 | $0.00049 |
Grade A, and why
decision-synthesis 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 4d 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: decision-synthesis
Decision Synthesis
Purpose
Combine independent reviews into a single, honest recommendation that a human can approve — without averaging away disagreement or inventing support.
When to use it
- At the synthesis step of
/council, after independent reports and one rebuttal round. - Whenever several reviewers' inputs must become one decision.
Instructions
- Restate the decision and the criteria (correctness, value, complexity, risk, reversibility, effort) before comparing options.
- Synthesize by argument strength and evidence, not by counting votes.
- Compare the leading option and at least one alternative against the criteria, citing the specific report behind each judgment.
- Preserve dissent: record minority positions and the conditions under which they would win.
- Assess how independent the deliberation actually was (parallel, sequential, or simulated) and let that cap the stated confidence.
- Use only evidence present in the reports; mark gaps as unknowns rather than filling them.
Output format
A decision record: recommended path, confidence (with deliberation mode), criteria
and scoring, rejected alternatives (with the reason each lost), key risks and
mitigations, preserved dissent, unresolved questions, and the next step
(/spec after human approval).
Anti-patterns
- Voting or averaging instead of weighing evidence.
- Hiding dissent to manufacture consensus.
- Inventing evidence absent from the reports.
- Overstating confidence when deliberation was simulated, not independent.
Verification checklist
- Criteria are stated and options scored against them with citations.
- Every claim traces to a specialist report; gaps are marked unknown.
- Dissent and the deliberation mode are recorded; confidence reflects them.
- The record ends at the human-approval gate.
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.
- 4d ago First seen · 54 lines · 14 tokens per session scan A 8cb0d73d55db
decision-synthesis 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 490 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-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.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.