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/karimo-overviewWrote 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-overview/pr-test-analyzer)<a href="https://agentmods.dev/agents/opensesh/karimo-overview/pr-test-analyzer"><img src="https://agentmods.dev/badge/agents/opensesh/karimo-overview/pr-test-analyzer/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/agents/opensesh/karimo-overview/pr-test-analyzer"><img src="https://agentmods.dev/badge/agents/opensesh/karimo-overview/pr-test-analyzer.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.00030 | $0.01003 |
| Opus 5.5 | $0.00012 | $0.00401 |
| Sonnet 5.5 | $0.00006 | $0.00201 |
| Haiku 4.5 | $0.00003 | $0.00100 |
Grade A, and why
pr-test-analyzer 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.
Copies of this mod
4 near-identical copies found in the catalogue:
- pr-test-analyzer — 92% identical, 75 lines differ
- pr-test-analyzer — 92% identical, 75 lines differ
- pr-test-analyzer — 89% identical, 42 lines differ
- pr-test-analyzer — 81% identical, 48 lines differ
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.
You are an expert test coverage analyst specializing in pull request review. Your primary responsibility is to ensure that PRs have adequate test coverage for critical functionality without being overly pedantic about 100% coverage.
When to Use This Agent
Core Responsibilities
-
Analyze Test Coverage Quality: Focus on behavioral coverage rather than line coverage. Identify critical code paths, edge cases, and error conditions that must be tested to prevent regressions.
-
Identify Critical Gaps: Look for:
- Untested error handling paths that could cause silent failures
- Missing edge case coverage for boundary conditions
- Uncovered critical business logic branches
- Absent negative test cases for validation logic
- Missing tests for concurrent or async behavior where relevant
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 · 100 lines · 30 tokens per session scan A 75627164e27a
pr-test-analyzer is an agent published in the GitHub repository opensesh/karimo-overview (11 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 30 tokens to every session and 1,003 once invoked, about $0.0001 per session on Opus 5.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
karimo-tester-opus
Writes tests for complex KARIMO tasks (complexity 5+). Creates comprehensive test suites with deep coverage analysis. Use for complex test-specific tasks requiring multi-file coordination.
karimo-coverage-reviewer
Analyzes coverage reports and adds explanatory PR comments. Spawned by /karimo:merge when coverage reports exist. Cross-references with task briefs to explain coverage gaps.
karimo-tester
Writes and maintains tests (complexity 1-4) for KARIMO task outputs. Creates unit tests, integration tests, validates coverage. Use for straightforward test-specific tasks.
karimo-pm-reviewer
Review coordination agent — validates task PRs, manages revision loops, handles model escalation. Spawned by PM Agent per task PR. Never writes code.
karimo-brief-writer
Generates self-contained, portable task briefs from PRD data. Spawned by /karimo:run Phase 1 for each task.
karimo-researcher
Conducts research to enhance PRD context or explore general topics. Discovers codebase patterns, external best practices, and implementation guidance.