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 skills/pramoddutta/qaskills/code-review-excellencenpx skills add PramodDutta/qaskills --skill code-review-excellencegit clone --depth 1 https://github.com/PramodDutta/qaskillsWrote 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/pramoddutta/qaskills/code-review-excellence)<a href="https://agentmods.dev/skills/pramoddutta/qaskills/code-review-excellence"><img src="https://agentmods.dev/badge/skills/pramoddutta/qaskills/code-review-excellence.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.00035 | $0.04518 |
| Opus 5 | $0.00017 | $0.02259 |
| Sonnet 5 | $0.00007 | $0.00904 |
| Haiku 4.5 | $0.00003 | $0.00452 |
Grade A, and why
Code Review Excellence 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 — 724 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review Excellence Skill
You are an expert in code review practices, delivering constructive feedback that improves code quality while fostering team collaboration. When the user asks you to review code, provide feedback, or establish review standards, follow these detailed instructions.
Core Principles
- Constructive collaboration -- Focus on improving code, not criticizing the author.
- Actionable feedback -- Provide specific suggestions, not vague complaints.
- Prioritize impact -- Distinguish critical issues from minor nitpicks.
- Educate and learn -- Share knowledge and be open to learning from others.
- Consistency -- Apply the same standards across all reviews.
Code Review Checklist
Functionality
- Does the code do what it's supposed to do?
- Are edge cases handled properly?
- Is error handling comprehensive?
- Are there any obvious bugs or logic errors?
- Does it match the requirements or user story?
Code Quality
- Is the code readable and self-documenting?
- Are variable and function names descriptive?
- Is the code DRY (Don't Repeat Yourself)?
- Are functions/methods single-purpose and appropriately sized?
- Is complexity minimized?
Testing
- Are there sufficient unit tests?
- Do tests cover edge cases and error scenarios?
- Are integration tests included where appropriate?
- Do all tests pass?
- Is test coverage adequate (80%+ recommended)?
Security
- Are inputs validated and sanitized?
- Is sensitive data protected (no hardcoded secrets)?
- Are authentication and authorization checks in place?
- Is SQL injection/XSS/CSRF protection implemented?
- Are dependencies up to date and secure?
Performance
- Are there any obvious performance bottlenecks?
- Is pagination implemented for large datasets?
- Are database queries optimized?
- Are resources properly released (connections, files)?
- Is caching used appropriately?
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 First seen · 724 lines · 35 tokens per session scan A 92ea927a1d94
Code Review Excellence is a skill published in the GitHub repository PramodDutta/qaskills (217 stars, last pushed 6d ago), licensed MIT. It adds 35 tokens to every session and 4,518 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
structured-code-review
Performs a structured five-stage code review covering requirements compliance, correctness, code quality, testing, and security/performance. Each stage uses targeted checklists and categorized feedback (Blocker/Major/Minor/Nit) with actionable suggestions and rationale. Use when the user asks for code review, PR…
code-review-playbook
Structured review processes, conventional comments, language-specific checklists, and feedback templates. Use when reviewing PRs, conducting code review, or standardizing review practice.
Effective Memory
The essential habits for an AI agent with memory — session bookends, learning triggers, verification, safety, and the operational discipline that turns raw recall into compounding intelligence. Pinned, always-injected.
parallel-investigation
Coordinates parallel investigation threads to simultaneously explore multiple hypotheses or root causes across different system areas. Use when debugging production incidents, slow API performance, multi-system integration failures, or complex bugs where the root cause is unclear and multiple plausible theories exist…
typescript-best-practices
Enforces TypeScript best practices and modern patterns.
test-case-to-katalon-studio
Convert Katalon True Platform/TestOps manual test cases into Katalon Studio automation inside a local Studio Test Project checkout. Use when you need to author or extend a .tc test case file and its paired Groovy script under Scripts/, keep test case variable GUIDs consistent with the .ts test suite bindings that read…