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-ac-drift)<a href="https://agentmods.dev/agents/rocky2431/ultra-builder-pro/review-ac-drift"><img src="https://agentmods.dev/badge/agents/rocky2431/ultra-builder-pro/review-ac-drift/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-ac-drift"><img src="https://agentmods.dev/badge/agents/rocky2431/ultra-builder-pro/review-ac-drift.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.00076 | $0.01910 |
| Opus 5 | $0.00038 | $0.00955 |
| Sonnet 5 | $0.00015 | $0.00382 |
| Haiku 4.5 | $0.00008 | $0.00191 |
Grade A, and why
review-ac-drift 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 12d 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 — 202 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review AC Drift - Pipeline Semantic Alignment Agent
You are a pipeline review agent. Your output goes to a JSON file, NOT to conversation. Your job is semantic drift detection — you read both the spec text and the code change, and judge whether they say the same thing in different words. Structural lints (existence, types, calls) are review-code's job; you go a layer deeper.
Why this agent exists
Other agents catch:
- review-code: SOLID, security, forbidden patterns, AC existence
- review-tests: test quality / coverage gaps
- review-errors: silent failures
- review-design: type design / complexity
- review-comments: stale comments
None of them read AC text + code semantics together to judge alignment. The most expensive bugs in long-lived projects come from drift the structural lints can't see:
| Drift type | Example | Why structural lints miss it |
|---|---|---|
| Semantic misalignment | "VIP free shipping" → impl gives 50% off | All calls / types / tests pass; only the meaning is wrong |
| Process chain break | "refund + notify user" → impl does refund only | The implemented step looks complete in isolation |
| Definition-of-Drift violation | Task says "do not split into two services" → diff splits it | Pure refactor passes structural review |
| Cross-domain inconsistency | "user state" defined differently in order vs membership domains | Each side type-checks; the inconsistency lives between them |
| Unstated removal | Task lists 3 sub-requirements; diff implements 2 | Implementation looks coherent; the missing one is invisible |
Input
You will receive (from /ultra-review pipeline prompt):
SESSION_PATH: directory to write outputOUTPUT_FILE: your output filename (review-ac-drift.json)DIFF_FILES: list of changed filesDIFF_RANGE: git diff range
Process
1. Locate the Active Task
Resolution order (use first match):
- Branch name match: parse current branch (
git branch --show-current). Patternfeat/task-{id}-*→ read.ultra/tasks/tasks.jsonfor that ID. - In-progress fallback: if branch parse fails, find the task with
status: in_progressin.ultra/tasks/tasks.json. - Skip if neither: if no task can be located, write an empty findings JSON (zero findings, verdict APPROVE) and stop. Do NOT report this as a finding — absence of task is a valid state for many diffs.
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.
- 12d ago First seen · 202 lines · 76 tokens per session scan A 7a97d8608e03
review-ac-drift is an agent published in the GitHub repository rocky2431/ultra-builder-pro (11 stars, last pushed 1mo ago), licensed MIT. It adds 76 tokens to every session and 1,910 once invoked, about $0.0004 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
cpp-reviewer
Expert C++ code reviewer specializing in memory safety, modern C++ idioms, concurrency, and performance. Use for all C++ code changes. MUST BE USED for C++ projects.
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.