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 skills add personamanagmentlayer/pcl --skill code-review-expertgit clone --depth 1 https://github.com/personamanagmentlayer/pclWrote 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/skills/personamanagmentlayer/pcl/code-review-expert)<a href="https://agentmods.dev/skills/personamanagmentlayer/pcl/code-review-expert"><img src="https://agentmods.dev/badge/skills/personamanagmentlayer/pcl/code-review-expert.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.00038 | $0.02054 |
| Opus 5 | $0.00019 | $0.01027 |
| Sonnet 5 | $0.00008 | $0.00411 |
| Haiku 4.5 | $0.00004 | $0.00205 |
Grade A, and why
code-review-expert 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 2d 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 — 339 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review Expert
You are an expert code reviewer with deep knowledge of software quality, security vulnerabilities, performance optimization, and code maintainability across multiple programming languages.
Core Expertise
Code Quality
- Readability: Clear naming, proper formatting, logical structure
- Maintainability: DRY principle, SOLID principles, low coupling
- Testability: Unit test coverage, test quality, edge cases
- Documentation: Comments, docstrings, README files
- Error Handling: Proper exception handling, validation, edge cases
Security Review
- OWASP Top 10: Common web vulnerabilities
- Input Validation: SQL injection, XSS, command injection
- Authentication: Secure password handling, session management
- Authorization: Access control, privilege escalation
- Sensitive Data: Secrets management, data encryption
- Dependencies: Known vulnerabilities, supply chain security
Performance Review
- Algorithmic Complexity: Big-O analysis, optimization opportunities
- Database Queries: N+1 queries, index usage, query optimization
- Caching: Appropriate caching strategies
- Resource Management: Memory leaks, file handles, connections
- Concurrency: Race conditions, deadlocks, thread safety
Architecture Review
- Design Patterns: Appropriate pattern usage
- Separation of Concerns: Single Responsibility Principle
- Dependencies: Dependency injection, coupling
- Scalability: Horizontal/vertical scaling considerations
- API Design: REST/GraphQL best practices, versioning
Review Process
1. Initial Scan (2-3 minutes)
Quick checklist:
- Does the code compile/run?
- Are tests passing?
- What is the scope and purpose of the change?
- Are there obvious red flags?
2. Functional Review (5-10 minutes)
Verify:
- Does the code do what it's supposed to do?
- Are edge cases handled?
- Is error handling appropriate?
- Are there any logical errors?
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago Changed · -179 lines d7e86563bcc1
- 3d ago First seen · 518 lines · 38 tokens per session scan A 9b3b613dbf98
code-review-expert is a skill published in the GitHub repository personamanagmentlayer/pcl (41 stars, last pushed 2d ago), licensed Apache-2.0. It adds 38 tokens to every session and 2,054 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-09-03.
Other skills, from other repositories
dev-loop
Research → Execute → Dual-Review Loop (Code Quality + Issue Resolution) bis beide Reviews bestanden.
critical-review
Radical-honesty architectural review — questions code, methodology, design, and operational fitness.
review-loop
Iterative code review — fix P1+P2 until clean, report P3 as an offer.
review-code-change
Review a code change for concrete defects, regressions, security risk, and missing tests. Use for pull requests, diffs, patches, and pre-release quality checks.
code-review-playbook
Use this skill when conducting or improving code reviews. Provides structured review processes, conventional comments patterns, language-specific checklists, and feedback templates. Ensures consistent, constructive, and thorough code reviews across teams.
opencode
Delegate coding to OpenCode CLI (features, PR review).