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/raja21068/autoresearch/pr-test-analyzergit clone --depth 1 https://github.com/raja21068/AutoResearchWrote 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/raja21068/autoresearch/pr-test-analyzer)<a href="https://agentmods.dev/agents/raja21068/autoresearch/pr-test-analyzer"><img src="https://agentmods.dev/badge/agents/raja21068/autoresearch/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.1 | $0.00024 | $0.00210 |
| Opus 5 | $0.00012 | $0.00105 |
| Sonnet 5 | $0.00005 | $0.00042 |
| Haiku 4.5 | $0.00002 | $0.00021 |
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 5d 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.
This is a copy
95% identical to pr-test-analyzer — 3 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
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.
- 5d ago First seen · 46 lines · 24 tokens per session scan A abfe4088e493
pr-test-analyzer is an agent published in the GitHub repository raja21068/AutoResearch (2 stars, last pushed 3mo ago), licensed MIT. It adds 24 tokens to every session and 210 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 95% identical to pr-test-analyzer, differing in 3 lines, and is treated as a copy.
Other agents, from other repositories
build-agent-empty-input-diagnosis
Status: Resolved for interview injections. Date: 2026-08-10 Related PR: #818 (fix/preset-tui-slash-command) — same root class as the original /preset fix. Suspected sibling bug reported by user: During superpowers / brainstorm skill conversations, when the orchestrator asks for confirmation or work is interrupted…
codemap
Defines agent personalities (Orchestrator, Explorer, Librarian, etc.) and manages their configuration lifecycle. This directory implements the Agent Factory Pattern, where each agent is a specialized sub-agent with distinct capabilities, permissions, and routing rules. The Orchestrator agent (src/agents/index.ts)…
domain
How the engineering skills should consume this repo's domain documentation when exploring the codebase.
devops
Agent "devops" from rizvee/multimodel-dev-os, covering devops agent spec and focus areas.
planner
Agent "planner" from rizvee/multimodel-dev-os, covering planner agent spec, focus areas and primary tooling.
qa-tester
Agent "qa-tester" from rizvee/multimodel-dev-os, covering qa tester agent spec and focus areas.