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 muyen/vibe-to-prod --skill code-reviewgit clone --depth 1 https://github.com/muyen/vibe-to-prodWrote 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/muyen/vibe-to-prod/code-review)<a href="https://agentmods.dev/skills/muyen/vibe-to-prod/code-review"><img src="https://agentmods.dev/badge/skills/muyen/vibe-to-prod/code-review/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/muyen/vibe-to-prod/code-review"><img src="https://agentmods.dev/badge/skills/muyen/vibe-to-prod/code-review.svg" alt="Reviewed on agentmods" width="80" 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.00027 | $0.00491 |
| Opus 5.5 | $0.00011 | $0.00196 |
| Sonnet 5.5 | $0.00005 | $0.00098 |
| Haiku 4.5 | $0.00003 | $0.00049 |
Grade A, and why
code-review 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 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.
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.
What it actually says
Code Review Skill
Automatically reviews code quality when significant changes are made.
When to Activate
This skill should activate when:
- User writes or modifies 50+ lines of code
- User implements a new feature or handler
- User asks for code review or feedback
- Changes touch authentication, payments, or security
Review Dimensions
1. Security (Critical)
- No hardcoded secrets or credentials
- Input validation on all user inputs
- SQL injection / NoSQL injection prevention
- XSS prevention in any output
- Auth checks on protected endpoints
2. Project Patterns (Critical)
- Generated types used (not
map[string]interface{}) - Routes registered properly
- Response schemas defined correctly
- OpenAPI spec updated for API changes
3. Performance
- No N+1 queries
- Appropriate indexes for queries
- Reasonable pagination limits
- No unnecessary data fetching
4. Architecture
- Single responsibility principle
- Proper error handling
- Appropriate logging
- Testable design
5. Platform Specific
Backend (Go)
- Uses Echo framework patterns
- Proper middleware usage
- Structured logging with Zap
iOS (Swift)
- SwiftUI best practices
- Source files < 400 lines
- Proper state management
Android (Kotlin)
- Jetpack Compose patterns
- Proper DI configuration
- Feature parity with iOS
Web (TypeScript)
- Next.js conventions followed
- Proper typing (no
any) - React best practices
Output Format
## Code Review Summary
### Critical Issues
- [List any blocking issues]
### Warnings
- [List non-blocking concerns]
### Suggestions
- [List optional improvements]
### Pattern Compliance
- [Check against CLAUDE.md rules]
Reference
See .claude/commands/code-review.md for detailed review criteria.
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 · 88 lines · 27 tokens per session scan A ffd7eca4de0e
code-review is a skill published in the GitHub repository muyen/vibe-to-prod (34 stars, last pushed 6mo ago), licensed MIT. It adds 27 tokens to every session and 491 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-10-04.
Other skills, from other repositories
code-review
Architectural code review — coding standards, SOLID, testability, performance concerns.
tech-debt
Track, categorize and prioritize technical debt across the codebase — scans for debt indicators, maintains a register.
solid-principles
SOLID principles checklist with Java examples. Use when a class has too many responsibilities, an abstraction leaks, or a dependency points the wrong way, and when the user asks about Single Responsibility, Open/Closed, Liskov, Interface Segregation or Dependency Inversion. For naming, duplication and method length…
clean-code
Clean Code principles (DRY, KISS, YAGNI), naming, function design and readability. Use when code is hard to read, with long methods, unclear names, duplication or deep nesting. For how responsibilities are split across classes and which way dependencies point, use solid-principles instead.
concurrency-review
Review Java concurrency code for thread safety, race conditions, deadlocks, and modern patterns (Virtual Threads, CompletableFuture, @Async). Use when user asks "check thread safety", "concurrency review", "async code review", or when reviewing multi-threaded code.
architecture-review
Analyze Java project architecture at macro level - package structure, module boundaries, dependency direction, and layering. Use when user asks "review architecture", "check structure", "package organization", or when evaluating if a codebase follows clean architecture principles.