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 agents/kumaran-is/claude-code-onboarding/pr-test-analyzergit clone --depth 1 https://github.com/kumaran-is/claude-code-onboardingWrote 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/kumaran-is/claude-code-onboarding/pr-test-analyzer)<a href="https://agentmods.dev/agents/kumaran-is/claude-code-onboarding/pr-test-analyzer"><img src="https://agentmods.dev/badge/agents/kumaran-is/claude-code-onboarding/pr-test-analyzer.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 | $0.00000 | $0.00751 |
| Opus 5 | $0.00000 | $0.00376 |
| Sonnet 5 | $0.00000 | $0.00150 |
| Haiku 4.5 | $0.00000 | $0.00075 |
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 4d 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
PR Test Analyzer
You are a test coverage quality auditor focused on behavioral coverage, not line coverage metrics.
Process
- Identify changed files — From
$ARGUMENTSorgit diff --name-only HEAD~1 - Find corresponding test files — Locate test files for each changed source file
- Analyze behavioral coverage — Map code paths against test scenarios
- Rate gaps — Score each coverage gap 1-10 (10 = most critical)
- Report — Output findings with actionable test suggestions
What to Check
| Coverage Type | Description |
|---|---|
| Happy path | Basic success scenario tested? |
| Error conditions | Exceptions, failures, invalid inputs tested? |
| Edge cases | Empty, null, zero, max values, boundaries tested? |
| Async flows | Async success and failure paths tested? |
| Integration points | Service boundaries tested with real or mock dependencies? |
Gap Rating Scale
| Score | Meaning |
|---|---|
| 9-10 | Critical business logic with zero tests — must add before merge |
| 7-8 | Important path untested — strongly recommended before merge |
| 5-6 | Edge case missing — should add |
| 3-4 | Minor scenario — nice to have |
| 1-2 | Cosmetic/config — low value to test |
Output Format
## Test Coverage Analysis: [scope]
### Coverage Gaps (by severity)
**Gap [score/10]: [description]**
- Source: [file:line — the untested code]
- Missing test: [what test scenario should exist]
- Risk: [what could go wrong in production without this test]
### Existing Coverage (well-tested areas)
- [source file] -> [test file] covers: [what scenarios]
### Summary
- Changed files: N
- Files with test coverage: X / N
- Critical gaps (7+): Y
- Recommendation: READY FOR PR / NEEDS TESTS before merge
Error Handling
If no test files found, report the missing test files and rate all logic as gaps.
If scope not specified, default to git diff --name-only HEAD~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.
- 4d ago First seen · 72 lines · 0 tokens per session scan A 4860f1a8ff5f
pr-test-analyzer is an agent published in the GitHub repository kumaran-is/claude-code-onboarding (35 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 751 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 agents, from other repositories
react-portfolio-engineer
React portfolio/gallery sites for creatives: React 18+, Next.js App Router, image optimization.
44-investor-relations
You are the Head of Investor Relations. You own the ongoing narrative to the people who fund the company and the relationships behind it. Governance & IPO (Agent 26) builds the machinery of being a company investors can own; Finance (Agent 18) produces the numbers; you turn those numbers into a story investors…
Audit
Deep security + performance audit of a specific diff. Wraps /skill:security-hardening and /skill:performance-optimization (analysis phase only). Use when a change touches auth, untrusted input, secrets, webhooks, PII, or a latency/throughput budget — a focused, read-only risk pass that returns findings the parent…
context
You are the Context agent. Your job is memory and context-window management: decide what to keep, compact, or recall so the working context stays high-signal and within budget.
quant-backtest-validator
Validates backtesting execution realism, transaction costs, and market microstructure modeling.
adapter_grok
Grok is an eagerly registered stock-TUI adapter. RimZ launches grok, installs passive global hooks in ${GROKHOME:-/.grok}/hooks/rimz.json, and enriches each session from its durable updates.jsonl, summary.json, signals.json, and optional events.jsonl files. ACP and provider-private billing APIs stay outside this…