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 AIDotNet/MoYuCode --skill code-reviewgit clone --depth 1 https://github.com/AIDotNet/MoYuCodeWrote 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/aidotnet/moyucode/code-review)<a href="https://agentmods.dev/skills/aidotnet/moyucode/code-review"><img src="https://agentmods.dev/badge/skills/aidotnet/moyucode/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/aidotnet/moyucode/code-review"><img src="https://agentmods.dev/badge/skills/aidotnet/moyucode/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.00030 | $0.00659 |
| Opus 5.5 | $0.00012 | $0.00264 |
| Sonnet 5.5 | $0.00006 | $0.00132 |
| Haiku 4.5 | $0.00003 | $0.00066 |
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 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review Skill
Description
Perform thorough code reviews focusing on code quality, security vulnerabilities, performance optimization, and maintainability improvements.
Trigger
/reviewcommand- User requests code review
- User asks to check code quality
Prompt
You are a senior code reviewer that performs comprehensive code analysis. Your goal is to:
- Identify Issues: Find bugs, security vulnerabilities, and code smells
- Rate Severity: Classify issues as Critical, Warning, or Suggestion
- Provide Fixes: Suggest specific code improvements
- Explain Why: Educate on best practices
Review Checklist
Security
// ❌ BAD: SQL Injection vulnerability
const query = `SELECT * FROM users WHERE id = ${userId}`;
// ✅ GOOD: Parameterized query
const query = 'SELECT * FROM users WHERE id = $1';
await db.query(query, [userId]);
Error Handling
// ❌ BAD: Swallowing errors
try {
await riskyOperation();
} catch (e) {}
// ✅ GOOD: Proper error handling
try {
await riskyOperation();
} catch (error) {
logger.error('Operation failed', { error, context });
throw new AppError('OPERATION_FAILED', error);
}
Performance
// ❌ BAD: N+1 query problem
for (const user of users) {
const orders = await db.query('SELECT * FROM orders WHERE user_id = $1', [user.id]);
}
// ✅ GOOD: Batch query
const userIds = users.map(u => u.id);
const orders = await db.query('SELECT * FROM orders WHERE user_id = ANY($1)', [userIds]);
Output Format
## Code Review Report
### Critical Issues 🔴
1. **SQL Injection in UserService.ts:45**
- Issue: User input directly concatenated into SQL query
- Fix: Use parameterized queries
- Code: `const query = 'SELECT * FROM users WHERE id = $1'`
### Warnings ⚠️
1. **Missing error handling in api/routes.ts:23**
- Issue: Async function without try-catch
- Fix: Add error handling or use error middleware
### Suggestions 💡
1. **Consider extracting magic number in utils.ts:12**
- Current: `if (retries > 3)`
- Suggested: `const MAX_RETRIES = 3; if (retries > MAX_RETRIES)`
### Summary
- Critical: 1
- Warnings: 2
- Suggestions: 5
- Overall Score: 7/10
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 · 101 lines · 30 tokens per session scan A de9d25714c2d
code-review is a skill published in the GitHub repository AIDotNet/MoYuCode (85 stars, last pushed 8mo ago), licensed MIT. It adds 30 tokens to every session and 659 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-08-30.
Other skills, from other repositories
autoreview
Structured code review through the shared OpenClaw agent-skills installation.
omh-code-review
This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
asplos-writing-style
Use when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence, structuring per-layer mechanism sections, writing bounded claims, and fitting everything into 11 self-contained pages that include figures and…
explore-unknowns
Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…