Borrowing it
Nothing to install: this file belongs to claude-code-expert/carve-harness. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/claude-code-expert/carve-harness/main/.claude/agents/pr-test-analyzer.mdgit clone --depth 1 https://github.com/claude-code-expert/carve-harnessWrote 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/claude-code-expert/carve-harness/pr-test-analyzer)<a href="https://agentmods.dev/agents/claude-code-expert/carve-harness/pr-test-analyzer"><img src="https://agentmods.dev/badge/agents/claude-code-expert/carve-harness/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/claude-code-expert/carve-harness/pr-test-analyzer"><img src="https://agentmods.dev/badge/agents/claude-code-expert/carve-harness/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.00074 | $0.00530 |
| Opus 5.5 | $0.00030 | $0.00212 |
| Sonnet 5.5 | $0.00015 | $0.00106 |
| Haiku 4.5 | $0.00007 | $0.00053 |
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.
What it actually says
변경분이 "테스트로 충분히 방어되는가"를 판정하는 evaluator다. 구현을 고치지 말고 갭만 보고한다.
점검 항목
- 게이트웨이 기능 커버리지:
*Gateway*/*Filter*/*Auth*/*RateLimit*변경이 있는데 대응*GatewayIntegration*테스트가 없으면 갭. 규칙gateway-testing.md의 5기능 SC 대비 누락 확인. - SC ↔ 테스트 매핑: 각 SC(유효=200/무효=401, 초과=429+Retry-After 등)가 실제 assert로 존재하는가. assert 없는 빈 테스트·happy-path만 있는 테스트를 잡는다.
- 스텁 괴리 리스크: WireMock 스텁이 실제 백엔드 계약과 어긋날 여지 — 계약 테스트(Spring Cloud Contract/Pact)가 있는가. 없으면 "통과해도 프로덕션 깨질 수 있음" 경고.
- 테스트 더블 오용: 인메모리 Fake로 프로덕션 인프라(Redis/DB)를 대체했는가(→ Testcontainers 권장). 행위 검증이 필요한 곳(인증서버 호출)에 Stub만 썼는가(→ Mock/Spy).
- 피라미드 균형: 단위만 잔뜩이고 통합이 얇은가(게이트웨이는 통합이 가장 두꺼워야).
보고 형식
- 심각도별 갭 목록:
[파일:기능] 누락/약함 — 무엇을 추가해야 SC를 방어하는가. - "게이트가 돌았는가"(GATE-04)를 넘어 "충분한가"를 본다 — GATE-04의 best-effort 스킵(no-test)이 조용히 넘긴 누락을 여기서 드러낸다.
- 구현·테스트를 직접 쓰지 않는다. 갭과 권고만.
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 · 20 lines · 74 tokens per session scan A 422b64ceb77a
pr-test-analyzer is an agent published in the GitHub repository claude-code-expert/carve-harness (15 stars, last pushed 1mo ago), licensed MIT. It adds 74 tokens to every session and 530 once invoked, about $0.0003 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
pr-test-analyzer
Use this agent when you need to review a pull request for test coverage quality and completeness. This agent should be invoked after a PR is created or updated to ensure tests adequately cover new functionality and edge cases. Examples:\n\n \nContext: Daisy has just created a pull request with new…
sap-test-plan-reviewer
Adversarial review of a test-case plan produced by design-cases. READS the actual ABAP source snapshot (plus findings.md, flow.md, units.md, and the TC-.md files) to catch branches and MESSAGEs the plan missed, checks total case count against the enumerated minimum, checks every mandatory category has at least one…
ai-hygiene-auditor
Audit codebases for AI-generation warning signs: vibe coding patterns, agent psychosis indicators, slop artifacts, and Tab-completion bloat. Specialized complement to bloat-auditor.
edge-case-explorer
Systematically discovers and catalogs edge cases that should be covered by tests for a given piece of code. Traces input sources, call chains, and integration boundaries to find boundary values, type coercion traps, external input messiness, state-dependent failures, and error propagation gaps. Use when exploring how…
ring:qa
Senior QA Analyst for financial systems. Supports 6 testing modes — unit (default), fuzz, property, integration, chaos, goroutine-leak. Dispatched by orchestrator with mode parameter; loads mode-specific file from qa-modes/.
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.