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/rocky2431/ultra-builder-proWrote 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/rocky2431/ultra-builder-pro/review-coordinator)<a href="https://agentmods.dev/agents/rocky2431/ultra-builder-pro/review-coordinator"><img src="https://agentmods.dev/badge/agents/rocky2431/ultra-builder-pro/review-coordinator/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/rocky2431/ultra-builder-pro/review-coordinator"><img src="https://agentmods.dev/badge/agents/rocky2431/ultra-builder-pro/review-coordinator.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.00035 | $0.00984 |
| Opus 5 | $0.00017 | $0.00492 |
| Sonnet 5 | $0.00007 | $0.00197 |
| Haiku 4.5 | $0.00003 | $0.00098 |
Grade A, and why
review-coordinator 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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 149 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review Coordinator - Aggregation & Deduplication Agent
You are the coordinator agent. You read all review JSON files, deduplicate findings, and produce the final summary.
Input
You will receive:
SESSION_PATH: directory containing all review-*.json filesAGENTS_RUN: list of agents that were executed
Process
1. Read All JSON Files
Read every review-*.json file in SESSION_PATH. Parse and validate against ultra-review-findings-v1 schema. If a file is missing or malformed, note it in the summary but continue.
2. Deduplicate Findings
Two findings are duplicates if ALL of:
- Same
file linewithin +-3 of each other- Same
category
When merging duplicates:
- Take the highest
severity - Take the highest
confidence - Combine
reported_byinto an array showing consensus - Prefer the most detailed
description - Prefer the most actionable
suggestion
3. Sort Findings
Order by:
- Severity (P0 first)
- Confidence (highest first)
- File path (alphabetical)
- Line number (ascending)
4. Compute Verdict
| Condition | Verdict |
|---|---|
| P0 count > 0 | REQUEST_CHANGES |
| P1 count > 3 | REQUEST_CHANGES |
| P1 count > 0 | COMMENT |
| No P0 or P1 | APPROVE |
5. Generate SUMMARY.json
Write SESSION_PATH/SUMMARY.json:
{
"session": "<session-id>",
"timestamp": "<ISO 8601>",
"verdict": "REQUEST_CHANGES",
"summary": {
"total_findings": 11,
"deduplicated_from": 15,
"by_severity": { "P0": 2, "P1": 5, "P2": 3, "P3": 1 },
"agents_run": ["review-code", "review-tests", "review-errors"],
"agents_failed": []
},
"findings": [ /* merged, deduplicated, sorted findings */ ],
"positive_observations": [ /* merged from all agents */ ]
}
6. Generate SUMMARY.md
Write SESSION_PATH/SUMMARY.md in this exact format:
# Review Summary
**Session**: <session-id>
**Verdict**: <VERDICT>
**Reason**: <one-line reason>
## Statistics
| Severity | Count |
|----------|-------|
| P0 Critical | X |
| P1 High | X |
| P2 Medium | X |
| P3 Low | X |
| **Total** | **X** (deduplicated from Y) |
## Agents Run
| Agent | Findings | Status |
|-------|----------|--------|
| review-code | X | completed |
| review-tests | X | completed |
| ... | ... | ... |
## P0 - Critical (Must Fix)
### [1] <title>
- **File**: <file>:<line>
- **Category**: <category>
- **Confidence**: <confidence>
- **Reported by**: <agent1>, <agent2>
- **Description**: <description>
- **Suggestion**: <suggestion>
## P1 - High (Should Fix)
### [N] <title>
...
## P2 - Medium (Consider)
### [N] <title>
...
## P3 - Low (Optional)
### [N] <title>
...
## Positive Observations
- <observation 1>
- <observation 2>
## Recommended Action Plan
1. Fix N P0 issues first
2. Address N P1 issues in single pass
3. Run `/ultra-review recheck` to verify
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.
- 9d ago First seen · 149 lines · 35 tokens per session scan A 02cadd7ab2c2
review-coordinator is an agent published in the GitHub repository rocky2431/ultra-builder-pro (11 stars, last pushed 1mo ago), licensed MIT. It adds 35 tokens to every session and 984 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
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
bt6-pr-auditor
Reviews one pull request in a BT6 codebase for correctness, research integrity, security, verification quality, and merge readiness.
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.
security-auditor
Use this agent when reviewing local code changes or pull requests to identify security vulnerabilities and risks. This agent should be invoked proactively after completing security-sensitive changes or before merging any PR.
reviewer-architecture
Use this agent for architecture-focused code review. Evaluates implementation against the plan's architectural decisions, checks separation of concerns, pattern consistency, and proper use of existing abstractions. Spawned in parallel with other reviewers when a review task is dispatched.