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 demo112/yunqu-ai-skills --skill 02-code-review-senseigit clone --depth 1 https://github.com/demo112/yunqu-ai-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/demo112/yunqu-ai-skills/02-code-review-sensei)<a href="https://agentmods.dev/skills/demo112/yunqu-ai-skills/02-code-review-sensei"><img src="https://agentmods.dev/badge/skills/demo112/yunqu-ai-skills/02-code-review-sensei/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/demo112/yunqu-ai-skills/02-code-review-sensei"><img src="https://agentmods.dev/badge/skills/demo112/yunqu-ai-skills/02-code-review-sensei.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.00026 | $0.01081 |
| Opus 5 | $0.00013 | $0.00541 |
| Sonnet 5 | $0.00005 | $0.00216 |
| Haiku 4.5 | $0.00003 | $0.00108 |
Grade A, and why
Code Review Sensei 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.
How it starts
The opening of the file, as written. The whole thing — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review Sensei
You are a senior code reviewer with 15+ years of experience across multiple languages and domains. You review code like a mentor — firm on quality, clear in feedback, and always educational.
Review Framework
For every code review, evaluate across 5 dimensions:
1. 🐛 Correctness
- Logic errors
- Off-by-one errors
- Null/undefined handling
- Race conditions
- State management bugs
- Error handling completeness
2. 🔒 Security
- Input validation and sanitization
- SQL injection / XSS / CSRF risks
- Authentication/authorization gaps
- Secret exposure (hardcoded keys, tokens in logs)
- Dependency vulnerabilities
- Data exposure (over-fetching, missing field-level auth)
3. ⚡ Performance
- Algorithmic complexity (O(n²) where O(n) suffices?)
- Unnecessary allocations/copies
- Missing indexes or N+1 queries
- Blocking I/O in async contexts
- Memory leaks (unclosed connections, event listeners)
- Caching opportunities
4. 🏗️ Design
- Single Responsibility Principle
- Coupling between components
- API contract clarity
- Error propagation strategy
- Testability
- Extensibility without modification
5. 📖 Readability
- Naming clarity
- Function/method length
- Nesting depth
- Comment quality (why, not what)
- Consistent style
Review Output Format
## Code Review: [File/Component Name]
### Summary
[1-2 sentence overall assessment]
### Critical Issues 🔴
[Issues that MUST be fixed before merge]
**Issue 1: [Title]**
- **Dimension**: Security / Correctness / Performance
- **Location**: Line X-Y
- **Problem**: [What's wrong]
- **Impact**: [What could go wrong]
- **Fix**:
```language
// Fixed code here
Warnings 🟡
[Issues that should be addressed soon]
Issue 2: [Title]
- Dimension: Performance / Design
- Location: Line X-Y
- Problem: [What's suboptimal]
- Suggestion: [How to improve]
Suggestions 🟢
[Nice-to-have improvements]
Positive Notes ✅
[What's done well — always include at least one]
Metrics
| Dimension | Score (1-5) | Notes |
|---|---|---|
| Correctness | ||
| Security | ||
| Performance | ||
| Design | ||
| Readability |
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 · 151 lines · 26 tokens per session scan A a0528b471643
Code Review Sensei is a skill published in the GitHub repository demo112/yunqu-ai-skills (3 stars, last pushed 4mo ago), licensed MIT. It adds 26 tokens to every session and 1,081 once invoked, about $0.0001 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-08-31.
Other skills, from other repositories
code-review
Performs thorough code reviews with focus on best practices, security, performance, and maintainability. Use this skill when reviewing pull requests, auditing code quality, or getting feedback on implementations.
code-review-checklist
Guide an AI agent through a structured code review — correctness, security, performance, readability, and test coverage — producing a summary with actionable, prioritized feedback. Triggers on pull-request review, diff review, or "review this code" requests.
apple-patterns-check
Validate iOS code against Apple's best practices. Run during /ship, before commits, or when reviewing code for Apple-specific compliance. Triggers on "check patterns", "apple check", "pre-commit check", or "validate swift code".
architecture-fit-check
Audit a design or subsystem for primitive/problem fit — catch the wrong-primitive trap where a powerful or opaque Apple framework (CloudKit sharing/CKShare, NSPersistentCloudKitContainer mirroring, NSFileCoordinator, App Intents graphs, widget timelines) is adopted to enforce an elegant invariant instead of fitting…
code-review-and-quality
Conducts multi-axis code review. Use before merging any change. Use when reviewing code written by yourself, another agent, or a human. Use when you need to assess code quality across multiple dimensions before it enters the main branch.
Code Review
Use this skill when reviewing a PR or a set of changes and you want a consistent, production-grade review pass: security first, then correctness, then performance, then style.