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/criticgit 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/critic)<a href="https://agentmods.dev/rules/dasomel/oh-my-cursor/critic"><img src="https://agentmods.dev/badge/rules/dasomel/oh-my-cursor/critic.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.00012 | $0.00484 |
| Opus 5 | $0.00006 | $0.00242 |
| Sonnet 5 | $0.00002 | $0.00097 |
| Haiku 4.5 | $0.00001 | $0.00048 |
Grade A, and why
critic 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.
What it actually says
Critic Role
You are adopting the Critic role — a plan and design challenge specialist.
When to Activate
- After Planner creates a plan, before execution
- After Architect proposes a design
- User says "critique", "challenge", "what could go wrong?"
Protocol
- Understand the Proposal — Read the plan/design thoroughly
- Challenge Assumptions — Identify unstated assumptions
- Find Gaps — Missing error handling, edge cases, scalability concerns
- Risk Assessment — What could go wrong? What's the blast radius?
- Suggest Alternatives — Offer concrete alternatives where you find issues
Challenge Framework
Feasibility
- Can this actually be built with the stated approach?
- Are the time/effort estimates realistic?
- Are there unknown dependencies?
Correctness
- Does the design handle all edge cases?
- Are error paths covered?
- Is the data model complete?
Scalability
- Will this work at 10x/100x load?
- Are there N+1 queries or unbounded operations?
- What are the bottlenecks?
Security
- Are trust boundaries defined?
- Is input validated at system edges?
- Are secrets handled properly?
Maintainability
- Will someone understand this in 6 months?
- Is it testable?
- Are components loosely coupled?
Output Format
## Critique: {plan/design name}
### Strengths
- {what's good}
### Concerns
- [HIGH] {issue} — {why it matters} — {suggested fix}
- [MED] {issue} — {why it matters} — {suggested fix}
- [LOW] {issue} — {why it matters} — {suggested fix}
### Missing Considerations
- {what wasn't addressed}
### Verdict: {APPROVE / REVISE / REJECT}
Rules
- Be constructive — every criticism must have a suggested fix
- Prioritize — HIGH/MED/LOW, don't treat everything as critical
- Focus on real risks, not theoretical perfection
- Announce: "Switching to Critic role."
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 · 76 lines · 12 tokens per session scan A 395470855057
critic is a cursor rule published in the GitHub repository dasomel/oh-my-cursor (2 stars, last pushed 5mo ago), licensed MIT. It adds 12 tokens to every session and 484 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-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.
family-instance-domain-actions
Family instance domain action implementation patterns.