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 commands/pr-pm/prpm/reviewgit clone --depth 1 https://github.com/pr-pm/prpmWhat 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.00007 | $0.00662 |
| Opus 5 | $0.00003 | $0.00331 |
| Sonnet 5 | $0.00001 | $0.00132 |
| Haiku 4.5 | $0.00001 | $0.00066 |
Grade A, and why
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.
How it starts
The opening of the file, as written. The whole thing — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Karen Repository Review
Perform a brutally honest Karen review with strictness level ${1:-5}/10.
Repository Scan
Scan for:
- Total files and lines of code
- TODO/FIXME/HACK comments
- Test files and coverage
- Documentation quality
Scoring (0-20 points each, total 0-100)
🎭 Bullshit Factor (0-20)
Assess over-engineering vs pragmatic simplicity:
- Check for unnecessary abstractions
- Identify premature optimization
- Look for architecture astronaut patterns
- Compare code complexity to problem complexity
⚙️ Actually Works (0-20)
Validate implementations fulfill stated objectives:
- Check core features are implemented
- Verify error handling exists
- Test edge case coverage
- Confirm README claims match reality
💎 Code Quality Reality (0-20)
Evaluate maintainability and developer experience:
- Check naming conventions
- Assess code organization
- Review documentation quality
- Identify technical debt
✅ Completion Honesty (0-20)
Measure finished work vs incomplete tasks:
- Count TODO/FIXME comments
- Check for half-done features
- Verify test completeness
- Assess polish level
🎯 Practical Value (0-20) [REQUIRES MARKET RESEARCH]
Distinguish genuine solutions from resume-padding:
- Search for "best [project-type] tools"
- Identify top 3-5 competitors (stars, downloads)
- Analyze unique value proposition
- Determine if project fills a real gap
Market Research (MANDATORY)
Before scoring Practical Value:
- Identify project type/category
- Search for competitors and alternatives
- Compare features and adoption
- Assess market gap vs duplication
Generate .karen/ Directory
Create:
.karen/score.json- Breakdown + total.karen/review.md- Full hot take with file:line refs.karen/history/YYYY-MM-DD-HH-MM.md- Timestamped archive.karen/badges/score-badge.svg- Visual indicator (if possible)
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.
- 2d ago First seen · 99 lines · 0 tokens per session scan A a20a3a65a3ef
review is a command published in the GitHub repository pr-pm/prpm (120 stars, last pushed 2mo ago), licensed MIT. It adds 7 tokens to every session and 662 once invoked, about $0.0000 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 commands, from other repositories
react
Apply React with TypeScript best practices.
nextjs
Apply Next.js App Router and React 19 patterns.
vue3
Apply Vue 3 with TypeScript and Composition API patterns.
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.