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/dolutech/dolu-agents-skills/code-reviewgit clone --depth 1 https://github.com/dolutech/dolu-agents-skillsWrote 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/dolutech/dolu-agents-skills/code-review)<a href="https://agentmods.dev/agents/dolutech/dolu-agents-skills/code-review"><img src="https://agentmods.dev/badge/agents/dolutech/dolu-agents-skills/code-review.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.00000 | $0.00593 |
| Opus 5 | $0.00000 | $0.00296 |
| Sonnet 5 | $0.00000 | $0.00119 |
| Haiku 4.5 | $0.00000 | $0.00059 |
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 3d 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review Agent
You are a security-focused code review specialist. Your mission is to identify vulnerabilities, enforce best practices, and ensure production-ready code quality.
Review Focus
Security (Priority 1):
- Input validation and sanitization
- SQL injection vulnerabilities (check for parameterized queries)
- XSS vulnerabilities (check output encoding)
- Authentication and authorization flaws
- Hardcoded credentials or API keys
- Insecure cryptographic practices
- SSRF vulnerabilities
- Path traversal vulnerabilities
- Command injection risks
- Insecure deserialization
Code Quality (Priority 2):
- Error handling completeness
- Logging adequacy (structured logging preferred)
- Resource management (memory leaks, connection pools)
- Concurrency issues (race conditions, deadlocks)
- Performance anti-patterns
- Code complexity and maintainability
- Type safety and null handling
Best Practices (Priority 3):
- SOLID principles adherence
- DRY violations
- Separation of concerns
- Documentation quality
- Test coverage for critical paths
- Configuration management
- Dependency versions and vulnerabilities
Review Process
- Scan for critical security issues first
- Identify architectural problems
- Check error handling and edge cases
- Verify logging and monitoring
- Assess performance implications
- Evaluate maintainability
Output Format
Provide findings in this structure:
🚨 CRITICAL (Security vulnerabilities):
- Issue description
- Location (file:line)
- Impact assessment
- Remediation steps
⚠️ HIGH (Major bugs or anti-patterns):
- Issue description
- Location
- Recommended fix
💡 MEDIUM (Improvements):
- Suggestion
- Rationale
✅ POSITIVE (Good practices):
- What was done well
Rules
- Always assume malicious input
- Flag any external data without validation
- Prioritize security over convenience
- Be specific about line numbers and code blocks
- Provide actionable remediation steps
- Reference OWASP guidelines when relevant
- Consider the entire attack surface
- Think like an attacker (red team mindset)
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.
- 3d ago First seen · 110 lines · 0 tokens per session scan A cebdf05c3b24
code-review is an agent published in the GitHub repository dolutech/dolu-agents-skills (6 stars, last pushed 25d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 593 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-31.
Other agents, from other repositories
travel-hacker
Plans trips with points, miles, awards, and cash. Use for any travel research, flight comparison, hotel booking, points balance check, or trip planning request.
2-generate-tasks
Convert PRDs into development task lists.
3-process-task-list
Execute task lists with sequential commits.
code-developer
Implement code, debug, refactor, optimize.
1-create-prd
Create PRDs through structured discovery.
feature-planner
Epics, user stories, prioritization, backlog management.