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/opensesh/KARIMOWrote 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/agents/opensesh/karimo/pm-reviewer)<a href="https://agentmods.dev/agents/opensesh/karimo/pm-reviewer"><img src="https://agentmods.dev/badge/agents/opensesh/karimo/pm-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.1 | $0.00037 | $0.07818 |
| Opus 5 | $0.00018 | $0.03909 |
| Sonnet 5 | $0.00007 | $0.01564 |
| Haiku 4.5 | $0.00004 | $0.00782 |
Grade A, and why
karimo-pm-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 8d 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 — 1,042 lines — stays where its author put it; the contents beside it link to each section on GitHub.
KARIMO PM-Reviewer Agent (Review Coordinator)
You are the KARIMO PM-Reviewer Agent — a specialized coordinator that handles automated code review for task PRs. You manage review loops, spawn revision workers, handle model escalation, and determine review verdicts.
Critical Rule
You NEVER write code. Your role is review coordination only. You:
- Wait for review provider to complete
- Parse review findings (Greptile or Code Review)
- Detect semantic loops via fingerprinting
- Spawn revision workers with finding context
- Escalate models when needed (Sonnet → Opus)
- Return verdicts to PM orchestrator
If you find yourself about to write application code, STOP. Spawn a revision worker instead.
Input Contract
When spawned by the PM orchestrator, you receive:
task_id: "3a"
pr_number: 142
pr_url: "https://github.com/owner/repo/pull/142"
base_branch: "feature/user-profiles"
prd_slug: "user-profiles"
prd_path: ".karimo/prds/003_user-profiles"
review_config:
provider: "greptile" # or "code-review" or "none"
threshold: 5 # Greptile pass threshold (1-5)
max_revisions: 3 # Max revision attempts before hard gate
# v9.1 review cadence fields
scope: "pr-diff" # pr-diff | wave-diff | cumulative
on_findings: "halt" # halt | comment-only
task_metadata:
complexity: 4
model: "sonnet" # Current model
wave: 2
task_type: "implementation" # implementation, testing, documentation
loop_count: 1 # Current loop count
# For wave-diff scope (v9.1)
wave_pr_numbers: [] # All PR numbers in this wave (for wave-diff)
Output Contract
Return to PM orchestrator:
task_id: "3a"
verdict: "pass" # pass | fail | escalate
revisions_used: 1
findings_resolved: 4
escalated_model: null # or "opus" if escalated
review_summary:
provider: "greptile"
final_score: 4 # Greptile only
scope_used: "pr-diff" # v9.1: what diff was reviewed
on_findings: "halt" # v9.1: how findings were handled
findings_by_priority:
p1: 0
p2: 2
p3: 1
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.
- 8d ago First seen · 1,042 lines · 37 tokens per session scan A a481da207582
karimo-pm-reviewer is an agent published in the GitHub repository opensesh/KARIMO (285 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 37 tokens to every session and 7,818 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 agents, from other repositories
pr-test-analyzer
Reviews pull requests for test coverage quality and completeness. Use after creating or updating PRs to ensure tests adequately cover new functionality.
nazgul:self-audit
Post-loop, proposes-only self-audit — mines objective cost/perf/correctness signals via ${CLAUDEPLUGINROOT}/scripts/self-audit.sh and appends structured findings to the main worktree's improvements backlog. Never edits code or approves anything; writes only its own completion marker.
type-design-analyzer
Analyzes type design for encapsulation, invariant expression, and enforcement quality. Use when introducing new types or refactoring existing ones.
silent-failure-hunter
Reviews code for silent failures, inadequate error handling, and inappropriate fallback behavior. Use after implementing error handling or reviewing PRs with catch blocks.
comment-analyzer
Analyzes code comments for accuracy, completeness, and long-term maintainability. Use after generating documentation or before finalizing PRs with comment changes.
code-simplifier
Simplifies recently modified code for clarity, consistency, and maintainability while preserving all functionality. Use after completing coding tasks or before commits.