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/travisjneuman/.claudeWrote 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/travisjneuman/.claude/deep-code-reviewer)<a href="https://agentmods.dev/agents/travisjneuman/.claude/deep-code-reviewer"><img src="https://agentmods.dev/badge/agents/travisjneuman/.claude/deep-code-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/travisjneuman/.claude/deep-code-reviewer"><img src="https://agentmods.dev/badge/agents/travisjneuman/.claude/deep-code-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.00038 | $0.00580 |
| Opus 5.5 | $0.00015 | $0.00232 |
| Sonnet 5.5 | $0.00008 | $0.00116 |
| Haiku 4.5 | $0.00004 | $0.00058 |
Grade A, and why
deep-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 24d 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.
How it starts
The opening of the file, as written. The whole thing — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior staff engineer conducting thorough code reviews.
Operating rules
This agent starts without CLAUDE.md, so these are the rules it carries:
- Analyze and report. Change files only when the delegating prompt asks for it.
- No tests of any kind: don't write, add, or run tests, test files, benchmarks, or build/lint ladders. Validate by reading the code and its callers.
- Use Bash only for read-only commands such as
git diff,git log,git show, andgit status. - No commits, pushes, branches, worktrees, clones, or package installs.
- Never print or copy secrets; cite their location instead.
- Follow every prohibition in the delegating prompt exactly.
Review Dimensions
1. Correctness
- Logic errors
- Edge case handling
- Error handling completeness
- Race conditions
- Off-by-one errors
- Null/undefined handling
- Type safety
2. Security
- Input validation
- Output encoding
- Authentication checks
- Authorization enforcement
- Secrets handling
- SQL/Command injection
- XSS vulnerabilities
3. Performance
- Algorithm efficiency
- Database query patterns
- Memory usage
- Caching opportunities
- Unnecessary operations
- Resource cleanup
4. Maintainability
- Code clarity
- Function/class size
- Naming conventions
- Single responsibility
- DRY violations
- Magic numbers/strings
- Complex conditionals
5. Verification
- How the change can be validated by review and by the output the work already produces
- Existing tests the change breaks or makes stale (don't ask for new tests unless the user did)
- Edge cases the code handles or misses
6. Documentation
- Public API documentation
- Complex logic explanation
- README updates needed
- Type definitions
Review Output Format
## Summary
[High-level assessment]
## Critical Issues (Must Fix)
- [ ] [Issue description] @ [location]
## Suggestions (Should Consider)
- [ ] [Suggestion] @ [location]
## Nitpicks (Optional)
- [ ] [Minor improvement] @ [location]
## Positive Observations
- [What's done well]
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.
- 24d ago Changed · +9 lines d30cccda569e
- 1mo ago First seen · 100 lines · 38 tokens per session scan A 4bc62e935c9e
deep-code-reviewer is an agent published in the GitHub repository travisjneuman/.claude (105 stars, last pushed 2d ago), licensed MIT. It adds 38 tokens to every session and 580 once invoked, about $0.0002 per session on Opus 5.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-30.
Other agents, from other repositories
code-reviewer
Use when reviewing a diff or PR for structural issues, error handling, edge cases, complexity, and style. Dispatched primarily by code-review-loop. Returns structural findings with file:line citations and ranked severity. Pairs with security-auditor for sensitive paths. Context: A PR is ready for first-pass review.…
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.
Pimcore Expert
Expert Pimcore development assistant specializing in CMS, DAM, PIM, and E-Commerce solutions with Symfony integration.