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/olo-dot-io/Uni-CLIWrote 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/commands/olo-dot-io/uni-cli/phase-review)<a href="https://agentmods.dev/commands/olo-dot-io/uni-cli/phase-review"><img src="https://agentmods.dev/badge/commands/olo-dot-io/uni-cli/phase-review/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/commands/olo-dot-io/uni-cli/phase-review"><img src="https://agentmods.dev/badge/commands/olo-dot-io/uni-cli/phase-review.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.00000 | $0.00466 |
| Opus 5.5 | $0.00000 | $0.00186 |
| Sonnet 5.5 | $0.00000 | $0.00093 |
| Haiku 4.5 | $0.00000 | $0.00047 |
Grade A, and why
phase-review 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.
What it actually says
/phase-review — cross-phase review before merge
Review a phase's worktree against the spec before merging into main.
Usage
/phase-review <phase-number>
Example: /phase-review 8 reviews Phase 8 output.
What it does
- Locates the phase's branch/worktree from
.claude/plans/sessions/. - Reads the spec section from
FINAL.md. - Runs
git log --oneline main..HEADto see all commits on the branch. - Runs
git diff main...HEAD --statfor a file-level summary. - For each deliverable in the spec, checks whether a matching commit exists and whether the expected files are present.
- Runs
npm run verifyone last time. - Returns one of:
DONE— every deliverable present, verify green.DONE_WITH_CONCERNS— all deliverables present, but something non-blocking is off (test count lower than promised, skipped tests without comments, etc.).NEEDS_CONTEXT— cannot verify against spec (missing FINAL.md, ambiguous deliverable).BLOCKED— a deliverable is missing or verify fails.
Ground rules
- Never approve a phase that claims files exist when they do not.
- Never approve a phase where
npm run verifyfailed locally. - Trust the spec, not the implementer's summary.
- Show evidence: commit SHAs, file paths, test count deltas.
Output shape
Phase N review: <DONE | DONE_WITH_CONCERNS | NEEDS_CONTEXT | BLOCKED>
Commits: <count> (SHAs: abc1234, def5678, ...)
Files touched: <count> (<adds> additions, <dels> deletions)
Test delta: +<n> new tests
Verify: <green | red with first error>
Deliverables:
8.1 [✓] Changesets + verify-changesets gate
8.2 [✓] OIDC npm publish + --provenance
...
Concerns: <none | bulleted list>
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 · 56 lines · 0 tokens per session scan A 089408ebea50
phase-review is a command published in the GitHub repository olo-dot-io/Uni-CLI (235 stars, last pushed 2d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 466 tokens. 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 commands, from other repositories
review-arch
Run a full architecture drift audit — finds architecture docs, scans code, compares against implementation, and produces a detailed drift report.
arch-diff
Quick architecture drift summary — counts drift items by severity without producing a full report.
ia-verify
Run pre-PR verification chain: build, types, lint, tests, security scan, diff review.
announce
Draft X/Twitter announcement post (or thread) for the latest plugin release.
check-architecture
Angular Architecture Review.
telemetry
Inspect, opt in/out of, and audit mochi's anonymous usage telemetry.