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 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/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<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="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Privilege Escalation · line 442 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- high Privilege Escalation · line 443 Code accesses credential files (SSH keys, AWS credentials, etc.). This could indicate credential theft attempts.Fix: Remove references to credential paths. Use environment variables or secrets managers. For docs, use placeholder paths (e.g., /path/to/config). Never load .env or token files in production code paths.
- medium MCP Rug Pull · line 566 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.5 | $0.00014 | $0.01807 |
| Sonnet 5.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 1mo 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.
- 1mo 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 (240 stars, last pushed 4d ago), licensed MIT. It adds 35 tokens to every session and 4,518 once invoked, about $0.0001 per session on Opus 5.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-expert
Expert-level code review focusing on quality, security, performance, and maintainability. Use this skill for conducting thorough code reviews, identifying issues, and providing constructive feedback.
code-auditor
Independent pre-merge review of a git diff, PR, or named files. Use when the user asks to review a PR, inspect current git changes, or hunt functional regressions, missed scenarios, wrong assumptions, concurrency bugs, and test gaps as an independent reviewer who does not defend the author's approach /…
Code Review Checklist
Runs a systematic checklist review on any code diff or file, covering correctness, security, performance, and readability.
quality-standard
Quality Standard Protocol: Defines the senior architect mindset that all other skills must follow. Enforces self-verification, edge case analysis, decomposition rules, anti-pattern awareness, and quality gates. This skill is NOT triggered directly — it is referenced by other skills to ensure every output has the…
code-review
Use before merging a diff. A structured review pass for correctness bugs, safety issues, and needless complexity.