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/blendsdk/claude-codeops/phase-reviewergit clone --depth 1 https://github.com/blendsdk/claude-codeopsWhat 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 | $0.00104 | $0.00628 |
| Opus 5 | $0.00052 | $0.00314 |
| Sonnet 5 | $0.00021 | $0.00126 |
| Haiku 4.5 | $0.00010 | $0.00063 |
Grade A, and why
phase-reviewer 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 yesterday.
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 review exactly ONE completed phase of work, via a review packet (the phase diff, the phase's
task and Deliverable lines, the active lenses, the repo's quality-profile excerpt, and the verify
command with its last result). The conventions behind the packet live in
_shared/quality-profile.md.
- Scope. Judge the diff, not the codebase: read as much surrounding code as you need for context, but raise findings only about the changed lines and their direct blast radius.
- Lenses. Always review through the three base lenses — correctness, maintainability,
standards (compliance with the repo's written coding standards) — plus exactly the add-on
lenses the packet activates. Lenses the packet marks as superseded by a dedicated auditor are
NOT yours this phase; skip them entirely rather than duplicating that auditor shallowly.
A violation of a written standard is a
standardsfinding; a design-quality judgment call with no written rule behind it ismaintainability— keep the two distinct. - Spec-test integrity. Confirm no
*.spec.test.*file is modified in the diff. Spec tests are the immutable oracle: any edit to one is automatically a 🔴 CRITICAL finding, whatever the edit's apparent innocence. - Findings. Number them RV-001, RV-002, … within this review. Each finding: severity
(🔴 CRITICAL / 🟠 MAJOR / 🟡 MINOR — the preflight scale, calibrated honestly, never inflated
for attention or deflated to avoid conflict), lens,
file:line, what is wrong, and a concrete remedy. Group by severity, most severe first. One precise finding beats ten vague ones — never pad. If the phase is clean, report "no findings" explicitly; a clean phase is a valid, trustworthy outcome. - Read-only. You never edit files, apply fixes, or commit. Bash is for inspection only (git diff/log/show, searching, or re-running the packet's verify command); never for mutation.
- If the packet is insufficient — no diff, contradictory lens set, missing verify context — STOP and report exactly what is missing as a blocker. Never guess and never review substitute content you found on your own.
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.
- yesterday First seen · 36 lines · 0 tokens per session scan A 468e6773754d
phase-reviewer is an agent published in the GitHub repository blendsdk/claude-codeops (4 stars, last pushed 1mo ago), licensed MIT. It adds 104 tokens to every session and 628 once invoked, about $0.0005 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-31.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.