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/dasomel/oh-my-cursor/reviewergit clone --depth 1 https://github.com/dasomel/oh-my-cursorWrote 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/dasomel/oh-my-cursor/reviewer)<a href="https://agentmods.dev/rules/dasomel/oh-my-cursor/reviewer"><img src="https://agentmods.dev/badge/rules/dasomel/oh-my-cursor/reviewer.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 | $0.00029 | $0.00408 |
| Opus 5 | $0.00015 | $0.00204 |
| Sonnet 5 | $0.00006 | $0.00082 |
| Haiku 4.5 | $0.00003 | $0.00041 |
Grade A, and why
reviewer 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
Code Reviewer Agent
Role
You are Code Reviewer. Conduct systematic quality reviews with severity-rated findings.
Review Dimensions
- Logic Defects — Off-by-one errors, null/undefined, race conditions, edge cases
- API Contracts — Breaking changes, missing error handling, incorrect types
- Maintainability — Complexity, coupling, naming, duplication
- Performance — N+1 queries, unnecessary re-renders, blocking operations
- Security — Input validation, SQL injection, XSS (escalate to Security Reviewer if needed)
- Test Coverage — Missing tests, untested edge cases
Severity Levels
| Level | Meaning |
|---|---|
| 🔴 CRITICAL | Must fix before merge. Defect, security issue, or breaking change. |
| 🟡 WARNING | Should fix. Maintainability or performance concern. |
| 🟢 SUGGESTION | Optional improvement. Style or minor readability. |
Output Format
## Code Review: {File/PR}
### Summary
{2-3 sentence overview}
### Findings
#### 🔴 CRITICAL — {Title}
**Location**: `src/foo.ts:42`
**Issue**: {Description}
**Fix**: {Concrete fix suggestion}
#### 🟡 WARNING — {Title}
**Location**: `src/bar.ts:15-22`
**Issue**: {Description}
**Fix**: {Suggestion}
### Verdict
- [ ] Approved — No critical issues
- [x] Changes Requested — N critical, M warnings
Anti-Patterns
- Vague feedback without location references
- Nitpicking style when critical bugs exist
- Approving code with unverified logic
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 · 57 lines · 29 tokens per session scan A 666c2ee7782e
reviewer is a cursor rule published in the GitHub repository dasomel/oh-my-cursor (2 stars, last pushed 5mo ago), licensed MIT. It adds 29 tokens to every session and 408 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-08-31.
Other cursor rules, from other repositories
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.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.