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/minimal-diff)<a href="https://agentmods.dev/rules/oriolshhh/runware-image-mcp/minimal-diff"><img src="https://agentmods.dev/badge/rules/oriolshhh/runware-image-mcp/minimal-diff/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/minimal-diff"><img src="https://agentmods.dev/badge/rules/oriolshhh/runware-image-mcp/minimal-diff.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.00008 | $0.00345 |
| Opus 5 | $0.00004 | $0.00172 |
| Sonnet 5 | $0.00002 | $0.00069 |
| Haiku 4.5 | $0.00001 | $0.00034 |
Grade A, and why
minimal-diff 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.
What it actually says
Pack: minimal-diff (enabled)
This pack is enabled; its guidance is composed into the core rule.
Pack: Minimal Diff
Behavioral goal
Make the smallest change that fully satisfies the task and keeps diffs reviewable.
Rules
- Change only what the task requires; avoid drive-by refactors and reformatting.
- Preserve public APIs and existing behavior unless the task requires a change.
- Propose larger refactors separately instead of bundling them.
Priorities
Default-on, low priority (20): applied early so stronger layers can refine it.
Boundaries
Tunes how much you change, never whether the change is correct or safe.
Possible conflicts
May tension with refactor-heavy work; defer to the spec when a refactor is required.
Enable when / avoid when
- Keep enabled for fixes, incremental features, and shared or legacy code.
- Disable or explicitly override only when an approved spec requires a broad migration or refactor.
Observable effect
The diff contains only required implementation, tests, and generated artifacts; unrelated cleanup is proposed separately.
Never override
Correctness, safety, repository conventions, or explicit user instructions.
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.
- 5d ago First seen · 45 lines · 8 tokens per session scan A a0b55db77611
minimal-diff is a cursor rule published in the GitHub repository Oriolshhh/runware-image-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 8 tokens to every session and 345 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
git-commit-attribution
Git commits must use the human developer identity only; never Cursor Agent co-authorship.
skill-management
A repository rule for managing coding-agent skills across their source files, generated copies, and version lock file. It treats third-party skills as part of the project’s tracked behavior contract.
iris
GitHub operations specialist — branches, pull requests, issues, releases, tags. Called by zeus after review. Never pushes or merges without explicit human approval. Integrates with VS Code GitHub Pull Requests extension.
rebase-only-merged-agents
When rebasing after a merge, only rebase the agents whose branches you just merged. Do not rebase agents that are still running.
git-workflow
Rules for git operations, commit strategy, and GitHub CLI usage.
release-checklist
What to update with each code change or version release.