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 commands/jeremydev87/codingbuddy/code-reviewgit clone --depth 1 https://github.com/JeremyDev87/codingbuddyWhat 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.00000 | $0.00281 |
| Opus 5 | $0.00000 | $0.00140 |
| Sonnet 5 | $0.00000 | $0.00056 |
| Haiku 4.5 | $0.00000 | $0.00028 |
Grade A, and why
code-review 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.
What it actually says
Code Review Command
Description
Comprehensive code quality evaluation using Code Reviewer Agent framework.
Command
# Read evaluation framework
READ packages/rules/.ai-rules/agents/code-reviewer.json
# Analyze implementation
ANALYZE recent changes:
- Git diff and status
- Code quality metrics
- Test coverage report
- Architecture compliance
# Apply anti-sycophancy rules
EVALUATE objectively:
- Find at least 3 improvement areas
- Use evidence-based assessment
- Reference measurable metrics
- Challenge design decisions
# Multi-dimensional review
ASSESS from perspectives:
- Code Quality (SOLID, DRY, complexity)
- Architecture (layer boundaries, dependencies)
- Security (XSS/CSRF, authentication)
- Performance (bundle size, optimization)
- Accessibility (WCAG 2.1 AA compliance)
- Test Quality (90%+ coverage, TDD workflow)
# Generate improvement plan
CREATE todo list with priorities:
- Critical issues (must fix)
- High priority improvements
- Medium/low enhancements
# Output in Korean
RESPOND in Korean (한국어)
Usage
# In OpenCode CLI
/code-review
Anti-Sycophancy Rules
- No praise without evidence
- Start with problems, not praise
- Identify measurable gaps
- Provide actionable solutions
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 · 54 lines · 0 tokens per session scan A 56ba50d683e9
code-review is a command published in the GitHub repository JeremyDev87/codingbuddy (31 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 281 tokens. 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 commands, from other repositories
extract
Analyze conversation history and extract reusable skills, commands, or agents.
codex-review
Run OpenAI Codex code review on current changes or a specific branch/commit.
raw-export
Export raw conversation data directly from JSONL session files.
stats
Show statistics for saved conversation files.
update-plugins
Batch update all installed Claude Code plugins to latest versions.
setup
Initialize or update chat-saver configuration for the current project.