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.
npx agentmods add rules/oriolshhh/runware-image-mcp/code-reviewgit 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/code-review)<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="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.00010 | $0.00347 |
| Opus 5 | $0.00005 | $0.00173 |
| Sonnet 5 | $0.00002 | $0.00069 |
| Haiku 4.5 | $0.00001 | $0.00035 |
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 2d 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
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:lineand 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-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.
- 2d ago First seen · 44 lines · 10 tokens per session scan A f5d7b69309f0
code-review is a cursor rule published in the GitHub repository Oriolshhh/runware-image-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 10 tokens to every session and 347 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.