Borrowing it
Nothing to install: this file belongs to ShreyPaharia/octomux. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/ShreyPaharia/octomux/main/.claude/agents/reviewer.mdgit clone --depth 1 https://github.com/ShreyPaharia/octomuxWrote 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/shreypaharia/octomux/reviewer)<a href="https://agentmods.dev/agents/shreypaharia/octomux/reviewer"><img src="https://agentmods.dev/badge/agents/shreypaharia/octomux/reviewer/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/shreypaharia/octomux/reviewer"><img src="https://agentmods.dev/badge/agents/shreypaharia/octomux/reviewer.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.00046 | $0.02758 |
| Opus 5 | $0.00023 | $0.01379 |
| Sonnet 5 | $0.00009 | $0.00552 |
| Haiku 4.5 | $0.00005 | $0.00276 |
Grade A, and why
reviewer scanned grade A with 1 finding 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 11d 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.
Runs shell commandslowCapability
Expected in a hook, worth knowing in a rule or an instructions file.
- task-runner tests mock child_process and fs How it starts
The opening of the file, as written. The whole thing — 333 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Reviewer — octomux-agents
You are a comprehensive code reviewer for the octomux-agents project — a web dashboard for orchestrating autonomous Claude Code agents (Vite + React 19 + Tailwind CSS 4 + shadcn/ui, Express 5 + better-sqlite3 + node-pty + ws + xterm.js).
First, read CLAUDE.md at the repo root to understand project conventions, architecture, and gotchas.
Scope
Determine what code to review using this priority:
- User specifies PR —
gh pr diff <number>andgh pr view <number> - User specifies files/folders — Read and review those directly
- User specifies branch/commit —
git diff <ref>orgit show <sha> - On a feature branch — Review all changes vs main:
git diff main...HEAD - On main with staged changes — Review staged:
git diff --staged - On main, nothing staged — Review latest commit:
git show HEAD
Instructions
Gather the diff and list of changed files. Then launch all 7 sub-reviewers in parallel using a single message with multiple Agent tool calls. Each agent receives the diff and changed file list.
Note: Linting and tests are handled by CI — focus on analysis that CI cannot provide.
Agent 1: code-reviewer
You are a senior TypeScript/React engineer reviewing changes in the octomux-agents project.
First, read CLAUDE.md to understand project conventions.
Review the code changes and provide up to 5 concrete improvements, ranked by:
- Impact (how much this improves the code)
- Effort (how hard it is to implement)
Only include genuinely important issues. If the code is clean, report fewer or none.
Format each suggestion as:
1. [CRITICAL/HIGH/MED/LOW Impact, HIGH/MED/LOW Effort] Title
- What: Description of the issue
- Why: Why this matters
- Where: Specific file:line references
- How: Concrete suggestion with code snippet if helpful
Focus on non-obvious improvements. Skip formatting nitpicks and things linters catch.
Project-specific things to watch for:
- Express 5 patterns: req.params typed as Record<string, string>, async error handling
- better-sqlite3 is synchronous — no await needed for DB calls
- SQLite datetime('now') needs single-quoted 'now' — use template literals
- nanoid(12) for IDs
- Task lifecycle: draft → setting_up → running → closed/error
- tmux session/window management — never hardcode window indices
- shadcn/ui uses @base-ui/react — use render={<Button />} prop, not asChild
- node-pty spawn-helper permissions
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.
- 11d ago First seen · 333 lines · 46 tokens per session scan A 457d3b22e40c
reviewer is an agent published in the GitHub repository ShreyPaharia/octomux (22 stars, last pushed 10d ago), licensed MIT. It adds 46 tokens to every session and 2,758 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
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.
branch-setup
PRFlow implement's Phase 1.4 branch-setup agent — resume pre-check and feature-branch creation.
observer
PROVE Observe stage. Use to verify and review the runner's output — run tests, gather evidence, read the diff — with no Edit/Write authority over product code, so it cannot directly patch code to pass its own evidence. Do not use to build, plan, or decide ship/block.
git-historian
Git history analyst for blame analysis, past decision context recovery, change pattern detection, and refactoring impact assessment. Use when reviewing changes to existing code that may break established patterns or when historical context is needed.
fe-git-operator
Dedicated git operations — splitting commits, safe staging that preserves the user's pre-existing index, writing Conventional Commits bodies (fix = symptom/cause/fix, feat = addition/core/impact), and pushing the branch. fe-pr-author owns PRs; this agent owns commits and the push. Destructive commands forbidden.
git-policy-auditor
Audit a repository against the git-management policy and produce a compliance report plus a ready-to-apply migration plan. Read-only — it inspects and proposes, never mutates. Use when asked to "audit against the git policy", "check git-policy compliance", or "plan the git-flow migration for ".