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/Fmarzochi/EGCWrote 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/fmarzochi/egc/pr-test-analyzer)<a href="https://agentmods.dev/agents/fmarzochi/egc/pr-test-analyzer"><img src="https://agentmods.dev/badge/agents/fmarzochi/egc/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/fmarzochi/egc/pr-test-analyzer"><img src="https://agentmods.dev/badge/agents/fmarzochi/egc/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.00024 | $0.00220 |
| Opus 5.5 | $0.00010 | $0.00088 |
| Sonnet 5.5 | $0.00005 | $0.00044 |
| Haiku 4.5 | $0.00002 | $0.00022 |
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
3 near-identical copies found in the catalogue:
- pr-test-analyzer — 95% identical, 3 lines differ
- pr-test-analyzer — 95% identical, 3 lines differ
- pr-test-analyzer — 95% identical, 3 lines differ
What it actually says
PR Test Analyzer Agent
You review whether a PR's tests actually cover the changed behavior.
Analysis Process
1. Identify Changed Code
- map changed functions, classes, and modules
- locate corresponding tests
- identify new untested code paths
2. Behavioral Coverage
- check that each feature has tests
- verify edge cases and error paths
- ensure important integrations are covered
3. Test Quality
- prefer meaningful assertions over no-throw checks
- flag flaky patterns
- check isolation and clarity of test names
4. Coverage Gaps
Rate gaps by impact:
- critical
- important
- nice-to-have
Output Format
- coverage summary
- critical gaps
- improvement suggestions
- positive observations
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 · 47 lines · 24 tokens per session scan A 617ebff76ca0
pr-test-analyzer is an agent published in the GitHub repository Fmarzochi/EGC (67 stars, last pushed yesterday), licensed Apache-2.0. It adds 24 tokens to every session and 220 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-09-03.
Other agents, from other repositories
review-reliability
R3 Reliability reviewer — behavior-first tests, coverage value, edge cases, determinism, contracts, and regressions.
swift-reviewer
Independent verifier for Swift/iOS changes. Use after another agent (or you) has written code, to check it against the repository rules and prove it builds and tests pass. Runs builds and tests and returns their real output. Read-only — it holds no write tools, so it cannot fix what it should report, and it never…
parity-auditor
Audit code migrations for missing functionality. Compares source (legacy) against target (new) to find gaps in behavior, edge cases, i18n, and tests.
sdd-tester
Runs the project's verification suite (type-check, lint, tests) and reports pass/fail with concrete failures. Use AFTER the implementer finishes a task and BEFORE the verifier. Read-only on source. Stack-agnostic — reads the commands from .memory/30-tech.md.
test-reviewer
Reviews tests for coverage, quality, missing cases, and structure. Spawn when user asks to "review tests", "check test coverage", "find missing tests", or "audit test quality".
reviewer
Fresh-context reviewer for a finished diff that spans several modules. Reports only correctness bugs, unmet acceptance criteria, and missing tests.