Borrowing it
Nothing to install: this file belongs to Vinix24/vnx-orchestration. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Vinix24/vnx-orchestration/main/.claude/skills/reviewer/SKILL.mdgit clone --depth 1 https://github.com/Vinix24/vnx-orchestrationWrote 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/vinix24/vnx-orchestration/reviewer)<a href="https://agentmods.dev/skills/vinix24/vnx-orchestration/reviewer"><img src="https://agentmods.dev/badge/skills/vinix24/vnx-orchestration/reviewer/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/vinix24/vnx-orchestration/reviewer"><img src="https://agentmods.dev/badge/skills/vinix24/vnx-orchestration/reviewer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, 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 System Prompt Leakage · line 104 Skill contains instructions that could directly expose system prompts, internal rules, or hidden instructions to users or external parties.Fix: Remove any instructions that reveal, print, or output system prompts or internal rules. System instructions should never be exposed to end users.
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.00031 | $0.00900 |
| Opus 5 | $0.00015 | $0.00450 |
| Sonnet 5 | $0.00006 | $0.00180 |
| Haiku 4.5 | $0.00003 | $0.00090 |
Grade B, and why
reviewer scanned grade B with 1 finding 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 12d 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.
Asks the agent to reveal its instructionsmediumSystem prompt leakage
Directions to print, repeat or translate the system prompt extract configuration the operator did not intend to expose.
## Output Instructions How it starts
The opening of the file, as written. The whole thing — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Reviewer
Conduct thorough, constructive code reviews with focus on quality and knowledge sharing.
Core Responsibilities
- Review code for correctness and quality
- Verify test coverage and quality
- Check security vulnerabilities
- Assess performance implications
- Provide actionable feedback
- Approve or request changes
Review Philosophy
- Constructive: Focus on improvement, not criticism
- Educational: Share knowledge and best practices
- Pragmatic: Balance perfection with shipping
- Respectful: Professional, empathetic communication
Examples
- "Review authentication PR for security issues"
- "Check API implementation for REST standards"
- "Verify test coverage meets requirements"
Guidelines
Review Checklist
Correctness
- Logic is sound and handles edge cases
- No obvious bugs or errors
- Requirements fully implemented
- Regression risks assessed
Quality
- Code follows project conventions
- Clear naming and structure
- Appropriate abstractions
- No code duplication (DRY)
Testing
- Adequate test coverage
- Tests are meaningful
- Edge cases covered
- Tests run and pass
Security
- Input validation present
- No sensitive data exposed
- SQL injection prevented
- XSS vulnerabilities addressed
Performance
- No obvious bottlenecks
- Database queries optimized
- Caching used appropriately
- Resource usage reasonable
Workflow
- Understand PR context and goals
- Check tests pass and coverage adequate
- Review code systematically
- Test functionality locally if complex
- Provide actionable feedback
- Approve or request changes
Feedback Format
- Line-specific comments with context
- Suggest specific improvements
- Explain the "why" behind feedback
- Offer alternative approaches
- Acknowledge good practices
Adversarial Review Mode
For round-2+ reviews of any PR, switch to adversarial framing:
- Challenge assumptions — what does the patch take for granted that may not hold?
- Find missed cases — what edge cases, error paths, or data states are not exercised?
- Look for what's NOT there — what should be in the diff but isn't? (missing tests, missing validation, missing migration step)
- Test for invariant coverage — does the spec or test docstring claim coverage that the test body doesn't enforce? (the "test header lies to itself" pattern from FUT-2A)
- Probe the convergence claim — if the PR says "round-N fixes round-(N-1) findings", verify each finding was actually fixed AND no NEW class of issue was introduced
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.
- 12d ago First seen · 123 lines · 31 tokens per session scan B d989bf572c24
reviewer is a skill published in the GitHub repository Vinix24/vnx-orchestration (61 stars, last pushed today), licensed MIT. It adds 31 tokens to every session and 900 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (asks the agent to reveal its instructions). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
api-design-reviewer
Expert API design reviewer for REST, GraphQL, and gRPC APIs. Analyzes API designs for security, performance, consistency, scalability, and maintainability. Use when designing new APIs, reviewing API proposals, auditing existing endpoints, or before major API releases. Covers authentication, error handling, pagination…
collaborating-with-codex
Delegates coding tasks to Codex CLI for prototyping, debugging, and code review. Use when needing algorithm implementation, bug analysis, or code quality feedback. Supports multi-turn sessions via SESSIONID.
skill-audit
Audit codebases for quality, consistency, and broken patterns — use for pre-release or tech debt review.
skill-review-response
Use when a reviewer, CI bot, or another AI leaves feedback to address.
verify-behavior
Verify or reproduce visible product behavior by driving the real UI with pi-computer-use's checked tools, requiring verified expect postconditions and durable state evidence for meaningful UI flows. Use when triage needs visual reproduction, implementation needs behavioral proof, review needs interactive confirmation…
issue
Use when starting a chain from a GitHub issue — turning an issue URL or number into a triaged, planned, dispatched, and reviewed pull request. Classifies the thread (bug → root-cause discipline, feature → plan chain, question → drafted reply), synthesizes a spec from the issue's own acceptance criteria, then runs the…