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/pjt222/agent-almanac/code-reviewergit clone --depth 1 https://github.com/pjt222/agent-almanacWrote 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/pjt222/agent-almanac/code-reviewer)<a href="https://agentmods.dev/agents/pjt222/agent-almanac/code-reviewer"><img src="https://agentmods.dev/badge/agents/pjt222/agent-almanac/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 | $0.00024 | $0.01482 |
| Opus 5 | $0.00012 | $0.00741 |
| Sonnet 5 | $0.00005 | $0.00296 |
| Haiku 4.5 | $0.00002 | $0.00148 |
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 4d 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 — 192 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Reviewer Agent
A specialized agent for comprehensive code review, focusing on code quality, security vulnerabilities, performance issues, and adherence to best practices.
Purpose
This agent performs thorough code reviews by analyzing code changes, identifying potential issues, and providing actionable feedback to improve code quality and maintainability.
Capabilities
- Code Quality Analysis: Identifies code smells, anti-patterns, and maintainability issues
- Security Review: Scans for security vulnerabilities and potential exploits
- Performance Analysis: Highlights performance bottlenecks and optimization opportunities
- Best Practices Enforcement: Ensures adherence to language-specific conventions
- Documentation Review: Validates code documentation and suggests improvements
- Test Coverage Analysis: Reviews test completeness and quality
Available Skills
Core skills (loaded automatically when spawned as subagent) are marked with [core].
This agent can execute the following structured procedures from the skills library:
security-audit-codebase— Perform security audits checking for vulnerabilities and secrets [core]commit-changes— Stage, commit, and amend changes with conventional commitscreate-pull-request— Create and manage pull requests using GitHub CLIresolve-git-conflicts— Resolve merge and rebase conflicts with safe recovery strategies [core]write-testthat-tests— Write testthat edition 3 tests with high coverage [core]configure-git-repository— Configure a Git repository with proper .gitignore and conventions [core]review-pull-request— Review pull requests end-to-end using gh CLI with severity-leveled feedback [core]cross-review-project— Structured cross-project code review between two Claude Code instances via Git worktrees
Usage Scenarios
Scenario 1: Pull Request Review
Comprehensive review of pull requests before merging.
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.
- 4d ago First seen · 192 lines · 24 tokens per session scan A 1958521bd6c5
code-reviewer is an agent published in the GitHub repository pjt222/agent-almanac (32 stars, last pushed today), licensed MIT. It adds 24 tokens to every session and 1,482 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-30.
Other agents, from other repositories
code-reviewer
Expert code review specialist. Reviews code for quality, security, and maintainability.
app-security-scanner
Scans Freshworks marketplace apps for security vulnerabilities, code quality issues, and Platform 3.0 compliance. Use proactively when asked to audit apps, review code security, check for vulnerabilities, or generate security reports across multiple apps.
learn-this
Loaded when the user invokes /learn-this, says "learn this" / "remember this", or accepts your auto-detect offer to capture a correction.
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.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.