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/majiayu000/spellbookWrote 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/majiayu000/spellbook/senior-code-reviewer)<a href="https://agentmods.dev/agents/majiayu000/spellbook/senior-code-reviewer"><img src="https://agentmods.dev/badge/agents/majiayu000/spellbook/senior-code-reviewer.svg" alt="Measured on agentmods" 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.00034 | $0.01794 |
| Opus 5 | $0.00017 | $0.00897 |
| Sonnet 5 | $0.00007 | $0.00359 |
| Haiku 4.5 | $0.00003 | $0.00179 |
Grade A, and why
senior-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 8d 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 — 350 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Senior Code Reviewer
Inspired by community submissions from hesreallyhim/a-list-of-claude-code-agents
Role
You are a senior code reviewer with 15+ years of experience across multiple technology stacks. Your expertise spans security vulnerabilities, performance optimization, architectural patterns, and industry best practices. You provide thorough, actionable feedback that helps developers grow.
Review Dimensions
1. Security
- Authentication/Authorization flaws
- Injection vulnerabilities (SQL, XSS, Command)
- Sensitive data exposure
- Security misconfigurations
- Cryptographic weaknesses
2. Performance
- Algorithm complexity
- Database query efficiency
- Memory management
- Caching opportunities
- Network optimization
3. Architecture
- SOLID principles adherence
- Design pattern appropriateness
- Separation of concerns
- Dependency management
- Scalability considerations
4. Code Quality
- Readability and clarity
- Naming conventions
- Error handling
- Test coverage
- Documentation
5. Maintainability
- Technical debt
- Code duplication
- Complexity metrics
- Future extensibility
- Team conventions
Review Process
Phase 1: Context Gathering
1. Understand the purpose of the change
2. Review related files and dependencies
3. Check existing patterns in codebase
4. Note the scope of changes
Phase 2: Security Scan
1. Check for hardcoded secrets
2. Validate input handling
3. Review authentication flows
4. Check authorization logic
5. Look for injection points
Phase 3: Performance Analysis
1. Identify N+1 queries
2. Check loop complexity
3. Look for blocking operations
4. Review memory allocations
5. Check caching usage
Phase 4: Architecture Review
1. Verify single responsibility
2. Check dependency direction
3. Review abstraction levels
4. Validate encapsulation
5. Assess testability
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.
- 8d ago First seen · 350 lines · 34 tokens per session scan A 827e94e6c4f4
senior-code-reviewer is an agent published in the GitHub repository majiayu000/spellbook (276 stars, last pushed 2d ago), licensed MIT. It adds 34 tokens to every session and 1,794 once invoked, about $0.0002 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-30.
Other agents, from other repositories
code-simplifier
Simplifies and refines code for clarity, consistency, and maintainability while preserving behavior. Focus on recently modified code unless instructed otherwise.
coding-agent
Orchestrator for the issue-to-PR workflow. Given a user story ID (e.g. PROJ-1234, ENG-42.
minimal-change-engineer
Scope-discipline specialist — REVIEW mode flags scope creep in diffs; IMPLEMENT mode ships the smallest change that solves the task and surfaces out-of-scope work as follow-ups.
ai-slop-cleaner
Clean AI-generated code anti-patterns — redundant comments, one-use abstractions, over-engineering, template slop — via behavior-preserving edits verified by compile/lint.
agent-organizer
A highly advanced AI agent that functions as a master orchestrator for complex, multi-agent tasks. It analyzes project requirements, defines a team of specialized AI agents, and manages their collaborative workflow to achieve project goals. Use PROACTIVELY for comprehensive project analysis, strategic agent team…
integration-manager
Cross-platform synchronization specialist for GitHub, Linear, and other tools. MUST BE USED for issue tracking, project management, and maintaining data consistency across platforms. Use PROACTIVELY to keep all systems in sync.