Vibe-Skills is a collection and routing system that helps AI agents discover, select, and coordinate specialized skills for completing tasks. It is intended for agents that need to organize workflows across many installed capabilities. The catalogue entries are skills and an agent belonging to this system.
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 foryourhealth111-pixel/Vibe-Skills --skill code-reviewergit clone --depth 1 https://github.com/foryourhealth111-pixel/Vibe-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/skills/foryourhealth111-pixel/vibe-skills/code-reviewer)<a href="https://agentmods.dev/skills/foryourhealth111-pixel/vibe-skills/code-reviewer"><img src="https://agentmods.dev/badge/skills/foryourhealth111-pixel/vibe-skills/code-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/foryourhealth111-pixel/vibe-skills/code-reviewer"><img src="https://agentmods.dev/badge/skills/foryourhealth111-pixel/vibe-skills/code-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 Privilege Escalation · line 150 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.
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.00058 | $0.01215 |
| Opus 5.5 | $0.00023 | $0.00486 |
| Sonnet 5.5 | $0.00012 | $0.00243 |
| Haiku 4.5 | $0.00006 | $0.00121 |
Grade A, and why
code-reviewer 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 — 232 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Reviewer
Complete toolkit for code reviewer with modern tools and best practices.
Routing Boundary
Use code-reviewer when the user asks for a fresh review of code or a PR:
- correctness and likely bugs
- maintainability and readability
- regression risk
- test coverage gaps from a reviewer's point of view
Do not let this skill own narrower problems:
security-reviewerowns OWASP, secret leak, auth bypass, injection, and dedicated security audit prompts.receiving-code-reviewowns existing CodeRabbit/GitHub/human review comments.verification-before-completionowns final evidence before claiming work is done.deslopowns cleanup of AI-generated comments, redundant guards, and boilerplate.tdd-guideowns test-first or RED -> GREEN -> REFACTOR development.
Migrated Legacy Assets
The legacy review wrapper has been absorbed into this direct route owner.
references/python-style-guide.mdcontains the retained Python naming, import, documentation, error-handling, and secret-handling guidance.scripts/check_style.pyis a lightweight stdin/string style checker for quick local review support.
Use these assets as supporting material inside code-reviewer; do not route to the deleted wrapper skill.
Quick Start
Main Capabilities
This skill provides three core capabilities through automated scripts:
# Script 1: Pr Analyzer
python scripts/pr_analyzer.py [options]
# Script 2: Code Quality Checker
python scripts/code_quality_checker.py [options]
# Script 3: Review Report Generator
python scripts/review_report_generator.py [options]
Core Capabilities
1. Pr Analyzer
Automated tool for pr analyzer tasks.
Features:
- Automated scaffolding
- Best practices built-in
- Configurable templates
- Quality checks
Usage:
python scripts/pr_analyzer.py <project-path> [options]
2. Code Quality Checker
Comprehensive analysis and optimization tool.
Features:
- Deep analysis
- Performance metrics
- Recommendations
- Automated fixes
What ships with it
8 files 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.
- references/code_review_checklist.md 1.6 KB
- references/coding_standards.md 1.6 KB
- references/common_antipatterns.md 1.6 KB
- references/python-style-guide.md 2.5 KB
- scripts/check_style.py 2.0 KB runs code
- scripts/code_quality_checker.py 3.1 KB runs code
- scripts/pr_analyzer.py 3.0 KB runs code
- scripts/review_report_generator.py 3.1 KB runs code
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 · 232 lines · 58 tokens per session scan A 242fde779909
code-reviewer is a skill published in the GitHub repository foryourhealth111-pixel/Vibe-Skills (3,770 stars, last pushed yesterday), licensed Apache-2.0. It adds 58 tokens to every session and 1,215 once invoked, about $0.0002 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-08-30.
Other skills, from other repositories
git-code-review
Review uncommitted or committed changes in the current branch and generate a code review report. Use when the user wants to review their changes before or after committing.
file-code-review
A code-review tool for specified files or pasted code. It checks the material against project conventions and creates a code review report, without needing the surrounding Git history.
agent-watchdog
Use when asked to watch, babysit, audit, review, compare, or fix another agent's work from a Codex session ID, Claude Code session/transcript, chat/thread link, PR, branch, log, or pasted run summary. Monitor until the other agent is done or blocked, reconstruct what the user asked, independently investigate the same…
comet-verify
Comet Phase 4: Verify and Close. Invoke with /comet-verify. Verify implementation matches design, handle development branch.
no-comments
Spawn Comment Sicko, fix accepted findings, and offer encodings for claimed constraints.
find-simplifications
Use when asked to find or plan Cherry Studio cleanup, simplification, refactoring, dead-code removal, duplicated state removal, unnecessary APIs, speculative generality, or library replacements, especially when the result should become evidence-backed proposed Agent Notes.