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/commands/pr-pm/prpm/compare)<a href="https://agentmods.dev/commands/pr-pm/prpm/compare"><img src="https://agentmods.dev/badge/commands/pr-pm/prpm/compare/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/commands/pr-pm/prpm/compare"><img src="https://agentmods.dev/badge/commands/pr-pm/prpm/compare.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.00000 | $0.00360 |
| Opus 5.5 | $0.00000 | $0.00144 |
| Sonnet 5.5 | $0.00000 | $0.00072 |
| Haiku 4.5 | $0.00000 | $0.00036 |
Grade A, and why
compare 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 1mo 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
Karen Comparative Analysis
Compare $1 vs $2 with brutal honesty.
Scan Both Projects
For each project:
- File count and structure
- Code quality patterns
- Test coverage
- Documentation
- TODO count
Scoring Comparison
Score each dimension (0-20) for both projects:
Project 1: $1
🎭 Bullshit Factor: X/20 ⚙️ Actually Works: X/20 💎 Code Quality: X/20 ✅ Completion: X/20 🎯 Practical Value: X/20 Total: X/100
Project 2: $2
🎭 Bullshit Factor: X/20 ⚙️ Actually Works: X/20 💎 Code Quality: X/20 ✅ Completion: X/20 🎯 Practical Value: X/20 Total: X/100
Head-to-Head Analysis
Winner: [Project name] by X points
Why:
- [Key differentiator 1 with file:line refs]
- [Key differentiator 2 with file:line refs]
- [Key differentiator 3 with file:line refs]
What the loser should steal:
- [Feature/pattern from winner]
- [Approach from winner]
What both should fix:
- [Common issue]
- [Common anti-pattern]
Recommendation
- Use $1 if: [Specific scenario]
- Use $2 if: [Specific scenario]
- Use neither if: Better alternatives exist (list them)
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.
- 1mo ago First seen · 64 lines · 0 tokens per session scan A 0bf30b72763d
compare is a command published in the GitHub repository pr-pm/prpm (123 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 360 tokens. 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
refactor-clean
Refactor provided code for cleanliness, maintainability, and alignment with SOLID principles and modern best practices — no over-engineering.
parallel-analyze
Multi-perspective analysis using parallel subagents. Analyzes code from architecture, security, performance, and testing viewpoints simultaneously.
parallel-review
Run parallel code review across multiple directories or files. Uses N subagents simultaneously for faster analysis.
review-code
Read ALL memory bank code rules + best practices, check the files that changed, and APPLY fixes so they adhere. The active counterpart to /scan (which is read-only). Use after an AI session, before commit, to make changed files compliant.
review-code
Agent review pass plus manual checklist for correctness, security, performance, and accessibility.
pr-description
Write a pull request description that helps reviewers: what changed, why, and how to verify, from a diff.