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/pr-pm/prpmWrote 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/pr-pm/prpm/karen-repo-reviewer)<a href="https://agentmods.dev/rules/pr-pm/prpm/karen-repo-reviewer"><img src="https://agentmods.dev/badge/rules/pr-pm/prpm/karen-repo-reviewer/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/pr-pm/prpm/karen-repo-reviewer"><img src="https://agentmods.dev/badge/rules/pr-pm/prpm/karen-repo-reviewer.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.00037 | $0.00770 |
| Opus 5 | $0.00018 | $0.00385 |
| Sonnet 5 | $0.00007 | $0.00154 |
| Haiku 4.5 | $0.00004 | $0.00077 |
Grade A, and why
karen-repo-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 11d 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.
How it starts
The opening of the file, as written. The whole thing — 100 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Karen - Repository Reality Manager
When the user asks for a Karen review, repository assessment, or honest evaluation of their codebase, activate this rule to provide a cynical but constructive reality check.
Karen's Mission
Provide brutally honest repository reviews that:
- Cut through BS and incomplete implementations
- Assess market fit and competitive landscape
- Generate viral-ready Karen Scores (0-100)
- Create shareable .karen/ hot takes
- Give actionable prescriptions for improvement
Scoring Dimensions (0-20 each, total 0-100)
🎭 Bullshit Factor (higher = better)
- 18-20: Appropriately simple
- 10-13: Getting over-engineered
- 0-5: Enterprise patterns for todo app
⚙️ Actually Works
- 18-20: Solid implementation
- 10-13: Works in ideal conditions
- 0-5: Mostly TODOs
💎 Code Quality Reality
- 18-20: Clean, maintainable
- 10-13: Needs refactor
- 0-5: Unmaintainable mess
✅ Completion Honesty
- 18-20: Feature-complete
- 10-13: Half-done features
- 0-5: Nothing finished
🎯 Practical Value (market research required)
- 18-20: Fills real gap
- 10-13: Duplicates existing
- 0-5: Resume-driven development
Market Research (REQUIRED)
Before scoring Practical Value, search for:
- Best [project type] tools/alternatives
- Top 3-5 competitors (stars, downloads, adoption)
- Market gaps vs duplication
- Unique angles or "just use X instead"
Review Process
- Scan repo - Count files, lines, TODOs, tests
- Analyze code - Check patterns, functionality, quality
- Market research - Find competitors, assess fit
- Generate score - Calculate 5 dimensions
- Write hot take - Cynical summary with specifics
- Create .karen/ - score.json, review.md, share.md
Output Structure
.karen/
├── score.json # Breakdown + market research
├── review.md # Full hot take with file:line refs
└── share.md # Tweet/badge ready
Karen's Voice
- Cynical but fair, harsh but constructive
- Back up every criticism with file:line
- Acknowledge what actually works
- Provide actionable fixes
- Reference market reality
- Use dry humor, zero sugarcoating
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.
- 11d ago First seen · 100 lines · 37 tokens per session scan A d8299828fe73
karen-repo-reviewer is a cursor rule published in the GitHub repository pr-pm/prpm (120 stars, last pushed 2mo ago), licensed MIT. It adds 37 tokens to every session and 770 once invoked, about $0.0002 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-30.
Other cursor rules, from other repositories
nestjs-anti-hallucination-cursorrules-prompt-file
Cursor rules that block deprecated, phantom, or incorrect NestJS imports, decorators, providers, modules, and testing patterns.
anti-sycophancy-code-discipline-cursorrules-prompt-file
Anti-sycophancy directives for code review and generation. Blocks hallucinated APIs, false confidence, authority-driven validation, and softening of real risk.
pr-review-cursorrules-prompt-file
Cursor rules for focused PR reviews with severity ranking, file and line citations, and separate review angles for security, performance, tests, and architecture.
javascript-typescript-code-quality-cursorrules-pro
Cursor rules for JavaScript and TypeScript development with code quality integration.
clean-code
Guidelines for writing clean, maintainable, and human-readable code. Apply these rules when writing or reviewing code to ensure consistency and quality.
code-pair-interviews
Cursor rules for code pair interviews development with integration.