A set of rules for examining code changes before they are merged into a project.

Use it to review a proposed change or check your own work, reporting reproducible blocking issues separately from optional suggestions.

It helps find correctness problems, missed requirements, weak tests, compatibility issues, and unrelated changes before they reach users.

code-review — Cursor rule for Cursor by Oriolshhh/runware-image-mcp

Install

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.

Clone the repo

git clone --depth 1 https://github.com/Oriolshhh/runware-image-mcp

Made for: Cursor.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/rules/oriolshhh/runware-image-mcp/code-review/github.svg)](https://agentmods.dev/rules/oriolshhh/runware-image-mcp/code-review)

Your own site

<a href="https://agentmods.dev/rules/oriolshhh/runware-image-mcp/code-review"><img src="https://agentmods.dev/badge/rules/oriolshhh/runware-image-mcp/code-review/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.

Your own site · 80×15

<a href="https://agentmods.dev/rules/oriolshhh/runware-image-mcp/code-review"><img src="https://agentmods.dev/badge/rules/oriolshhh/runware-image-mcp/code-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 10 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 347 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00010	$0.00347
Opus 5.5	$0.00004	$0.00139
Sonnet 5.5	$0.00002	$0.00069
Haiku 4.5	$0.00001	$0.00035

Measured 1mo ago against content hash f5d7b69309f0, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

code-review 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 1mo 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.

.cursor/rules/code-review.mdc · 44 lines

What it actually says

Skill: code-review

Code Review

Purpose

Find defects and risks in a diff before it merges, and communicate them so they are easy to act on.

When to use it

Reviewing any proposed change, or self-reviewing before requesting review.

Instructions

Read the spec, then the diff. Confirm each requirement is met.
Check correctness and edge cases first, style second.
Verify tests exist and actually exercise the new behavior.
Flag unrelated or out-of-scope changes.
Label each finding Blocking or Non-blocking.

Output format

Summary verdict.
Blocking findings with file:line and a concrete fix.
Non-blocking suggestions.

Anti-patterns

Mixing cosmetic nits with blocking defects without labels.
Approving without checking tests or the spec.
Rewriting the author's code instead of describing the fix.

Verification checklist

Trace changed inputs through success, failure, boundary, and concurrency paths.
Inspect call sites before claiming compatibility impact.
Confirm each finding is reproducible from the diff and repository evidence.
End with a verdict and explicitly state when no actionable finding exists.

Apply context-discovery before 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.

Changes

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.

1mo ago First seen · 44 lines · 10 tokens per session scan A f5d7b69309f0

Subscribe to this mod's changes

code-review is a cursor rule published in the GitHub repository Oriolshhh/runware-image-mcp (0 stars, last pushed 3mo ago), licensed MIT. It adds 10 tokens to every session and 347 once invoked, about $0.0000 per session on Opus 5.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.

Code review Testing

atmos-rules

This is a Golang CLI project using Cobra for command structure and Viper for configuration management. The project maintains high code quality standards through golangci-lint and aims for maximum test coverage. The repository also includes the website source code for https://atmos.tools.

cloudposse/atmos · 1,420 tokens

code-review