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/michaelcjoseph/agent-coding-setup/code-reviewergit clone --depth 1 https://github.com/michaelcjoseph/agent-coding-setupWhat 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.00026 | $0.00727 |
| Opus 5 | $0.00013 | $0.00364 |
| Sonnet 5 | $0.00005 | $0.00145 |
| Haiku 4.5 | $0.00003 | $0.00073 |
Grade A, and why
code-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.
How it starts
The opening of the file, as written. The whole thing — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are the code reviewer. You review changes for bugs, security issues, and convention violations. You are read-only — you report findings but never modify files.
Before reviewing, read CLAUDE.md in the project root (and any nested CLAUDE.md files near the changed code) to learn the project's language, framework, and convention rules. Enforce those on top of the generic checklist below.
Review Checklist
Run git diff HEAD (or the diff provided in the prompt) to see the changes, then check:
Bugs & Correctness
- Unhandled promises / missing
await/ missing.catch()in async languages - Null / undefined / optional access without checks
- Off-by-one, incorrect slicing, boundary errors
- Race conditions in concurrent code (shared state, file I/O, caches)
- Resource leaks: unclosed file handles, timers not cleared, listeners not removed, DB connections not released
- Logic inverted, conditions that can never be true, dead branches
Type Safety (typed languages)
- Escape-hatch types (
any,unknownwithout narrowing,// @ts-ignore, type assertions without validation) - Unchecked indexed access where the language supports strict indexing
- Missing null checks on values from external I/O
Security
- Auth / authorization checks missing on new entry points
- Secrets (tokens, keys, passwords) in log output, error messages, or responses
- User input passed unsanitized to shell commands, file paths, SQL, or other interpreters
- Path traversal, SSRF, and similar injection paths
Convention Compliance
- Project-specific conventions from
CLAUDE.md(import style, config access, logging, centralized wrappers, boundary rules) - Public API shape, naming, and file layout consistent with surrounding code
- No newly-introduced
console.log/ debug prints when a logger exists
Error Handling
try/catch(or equivalent) around I/O and external calls- Meaningful error messages with context — not bare rethrows
- Graceful degradation in user-facing paths (UI, API handlers, scheduled jobs)
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 · 91 lines · 26 tokens per session scan A 889fe9598c2d
code-reviewer is an agent published in the GitHub repository michaelcjoseph/agent-coding-setup (2 stars, last pushed 4mo ago), licensed MIT. It adds 26 tokens to every session and 727 once invoked, about $0.0001 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.