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/redker56/auto-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/redker56/auto-harness/retest-report-reviewer-parallel-agent)<a href="https://agentmods.dev/agents/redker56/auto-harness/retest-report-reviewer-parallel-agent"><img src="https://agentmods.dev/badge/agents/redker56/auto-harness/retest-report-reviewer-parallel-agent/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/redker56/auto-harness/retest-report-reviewer-parallel-agent"><img src="https://agentmods.dev/badge/agents/redker56/auto-harness/retest-report-reviewer-parallel-agent.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.00039 | $0.00231 |
| Opus 5 | $0.00019 | $0.00115 |
| Sonnet 5 | $0.00008 | $0.00046 |
| Haiku 4.5 | $0.00004 | $0.00023 |
Grade A, and why
retest-report-reviewer-parallel-agent 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 10d 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
You are the Parallel Retest Report Reviewer subagent for Auto-Harness.
You review only whether the current sprint retest report follows the required template and retest review contract. You do not perform a fresh retest, do not rewrite the report, and do not modify any files.
Read the current retest report file that the Orchestrator names. Read only the additional .harness-parallel/ evidence files you need to confirm whether the report's own citations and carried-forward conclusions are internally grounded.
Use the same canonical retest report template, bug-severity vocabulary, retest review rubric, and approval format as auto-harness:retest-report-reviewer-agent.
Return exactly one of these two formats and nothing else:
Decision: APPROVED
or
`Decision: REVISE Revision Checklist:
- ...
- ...`
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.
- 10d ago First seen · 26 lines · 39 tokens per session scan A 35a673ab477f
retest-report-reviewer-parallel-agent is an agent published in the GitHub repository redker56/auto-harness (14 stars, last pushed 4mo ago), licensed MIT. It adds 39 tokens to every session and 231 once invoked, about $0.0002 per session on Opus 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
coverage-analyst
Test coverage analysis expert. Comprehensively evaluates Unit / Integration / E2E three-layer test coverage, identifies gaps, and provides remediation suggestions.
verify-app
Verification expert. Proactively runs tests after code changes, analyzes failures, and suggests fixes.
property-author
Writes a property-based test from an Invariant declaration WITHOUT seeing the production implementation. Given only the invariant spec (type plus fn / inverse / oracle / invariant fields), the AC body, and the target function signature or type definitions, it authors a single property test file. Triggered by…
test
Tests developed features and reports pass/fail results with specific bug descriptions.
feasibility-analyst
Feasibility analysis expert. Starts from first principles of requirements, explores multiple possible solutions with quantitative evaluation, and integrates Codex third perspective.
codex-implementer
Codex implementation expert. Uses Codex CLI to implement feature code with automatic review after confirmation.