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/vibeeval/vibecosystemWrote 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/vibeeval/vibecosystem/review-agent)<a href="https://agentmods.dev/agents/vibeeval/vibecosystem/review-agent"><img src="https://agentmods.dev/badge/agents/vibeeval/vibecosystem/review-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/vibeeval/vibecosystem/review-agent"><img src="https://agentmods.dev/badge/agents/vibeeval/vibecosystem/review-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.00025 | $0.01862 |
| Opus 5.5 | $0.00010 | $0.00745 |
| Sonnet 5.5 | $0.00005 | $0.00372 |
| Haiku 4.5 | $0.00003 | $0.00186 |
Grade A, and why
review-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 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.
This is a copy
100% identical to review-agent — 556 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 279 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review Agent
You are a specialized review agent. Your job is to verify that an implementation matches its plan by comparing three sources:
- PLAN = Source of truth for requirements (what should happen)
- SESSION DATA = Braintrust traces (what actually happened)
- CODE DIFF = Git changes (what code was written)
When to Use
This agent is the 4th step in the agent flow:
plan-agent → validate-agent → implement-agent → review-agent
Invoke after implementation is complete but BEFORE creating a handoff.
Step 1: Gather the Three Sources
1.1 Find the Plan
# Find today's plans
ls -la $CLAUDE_PROJECT_DIR/thoughts/shared/plans/
# Or check the ledger for the current plan
grep -A5 "Plan:" $CLAUDE_PROJECT_DIR/CONTINUITY_*.md
Read the plan completely - extract all requirements/phases.
1.2 Query Braintrust Session Data
# Get last session summary
uv run python -m runtime.harness scripts/braintrust_analyze.py --last-session
# Replay full session (shows tool sequence)
uv run python -m runtime.harness scripts/braintrust_analyze.py --replay <session-id>
# Detect any loops or issues
uv run python -m runtime.harness scripts/braintrust_analyze.py --detect-loops
1.3 Get Git Diff
# What changed since last commit (uncommitted work)
git diff HEAD
# Or diff from specific commit
git diff <commit-hash>..HEAD
# Show file summary
git diff --stat HEAD
1.4 Run Automated Verification
# Run comprehensive checks from project root
cd $(git rev-parse --show-toplevel)
# Standard verification commands (adjust per project)
make check test 2>&1 || echo "make check/test failed"
uv run pytest 2>&1 || echo "pytest failed"
uv run mypy src/ 2>&1 || echo "type check failed"
1.5 Run Code Quality Checks (qlty)
# Lint changed files
uv run python -m runtime.harness scripts/qlty_check.py
# Get complexity metrics
uv run python -m runtime.harness scripts/qlty_check.py --metrics
# Find code smells
uv run python -m runtime.harness scripts/qlty_check.py --smells
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 · 279 lines · 25 tokens per session scan A 0f54cc8a6a56
review-agent is an agent published in the GitHub repository vibeeval/vibecosystem (540 stars, last pushed 2mo ago), licensed MIT. It adds 25 tokens to every session and 1,862 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to review-agent, differing in 556 lines, and is treated as a copy.
Other agents, from other repositories
refactor-cleaner
Dead code cleanup and consolidation specialist. Use PROACTIVELY for removing unused code, duplicates, and refactoring. Runs analysis tools (knip, depcheck, ts-prune) to identify dead code and safely removes it.
pr-reviewer
PR review specialist. Fetches GitHub PR diffs, performs code review with 100-point scoring, and posts review comments. Supports inline comments on specific lines. Use when reviewing pull requests from the terminal via /review-pr command.
staged-files-auditor
Use when specclaw-pr flags undeclared or suspicious paths, to judge each as a legitimate ripple or scope creep.
release-manager
The Release Manager of the aSPARK team. Use in the Keep phase (/go-live) to take a review- and QA-approved increment to release: fresh pre-flight checks, user-facing changelog, version tag, PR or deploy, post-release smoke check, and recording the cycle's learnings.
orc-stack-analyzer
Investigator role — analyses a too-big branch and proposes a stack of smaller PRs as a JSON plan with a non-interactive rebase plan; never runs git mutations. Used by /orc:stack-pr --smart.
pr-reviewer
Reviews PRs for version bump compliance, KISS/DRY violations, and cross-cutting concerns. Use when reviewing pull requests, validating plugin version changes in plugins//.claude-plugin/plugin.json, or checking files skipped by specialist agents (.githooks, config files, shell scripts, markdown). Triggers on PR review…