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 agentmods add skills/xiaowen-jiang/agent-enterprise/code_reviewnpx skills add Xiaowen-Jiang/agent-enterprise --skill code_reviewgit clone --depth 1 https://github.com/Xiaowen-Jiang/agent-enterpriseWrote 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/xiaowen-jiang/agent-enterprise/code_review)<a href="https://agentmods.dev/skills/xiaowen-jiang/agent-enterprise/code_review"><img src="https://agentmods.dev/badge/skills/xiaowen-jiang/agent-enterprise/code_review.svg" alt="Measured on agentmods" 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 | $0.00015 | $0.00292 |
| Opus 5 | $0.00008 | $0.00146 |
| Sonnet 5 | $0.00003 | $0.00058 |
| Haiku 4.5 | $0.00002 | $0.00029 |
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 4d 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
Process
- Read the target file(s) using the filesystem tools
- Security check: Look for SQL injection, XSS, command injection, hardcoded secrets, unsafe deserialization
- Code quality: Check naming conventions, function length, duplication, complexity
- Error handling: Verify edge cases, null checks, proper exception handling
- Style & readability: Consistent formatting, meaningful comments, clear variable names
- Performance: Identify obvious inefficiencies, unnecessary loops, memory issues
Output Format
Provide structured feedback using severity levels:
- CRITICAL: Security vulnerabilities or bugs that will cause failures
- WARNING: Code smells, potential issues, or maintainability concerns
- SUGGESTION: Style improvements, better patterns, or minor optimizations
- GOOD: Highlight well-written parts (positive feedback matters)
Guidelines
- Be specific — reference line numbers and exact code
- Explain WHY something is an issue, not just WHAT
- Suggest concrete fixes with code examples
- Start with a brief summary before detailed findings
- End with an overall assessment (approve / request changes)
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.
- 4d ago First seen · 34 lines · 15 tokens per session scan A 8ec96ac69922
Code Review is a skill published in the GitHub repository Xiaowen-Jiang/agent-enterprise (52 stars, last pushed 5mo ago), licensed MIT. It adds 15 tokens to every session and 292 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-30.
Other skills, from other repositories
compound-engineering
Orchestration layer that coordinates Debt-Sentinel, Red Team Tribunal, and Spec-Lock into unified workflows. Use when you need comprehensive quality assurance with multiple validation stages. Provides safe-edit workflows, CI pipelines, enhancement pipelines, and engineering metrics dashboard.
Verification Before Completion
Mandatory empirical verification suite execution before declaring task completion.
openspec-explore
Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.
release-openspec
Use this skill when releasing OpenSpec: audit merged work and changeset coverage, decide whether a catch-up changeset PR is needed, prepare or resume the Changesets Version Packages PR, cut a beta or stable release, verify publishing, and polish GitHub release notes. Also use when asked whether an open release PR is…
openspec-update-change
Update an OpenSpec change by revising its existing planning artifacts and keeping them coherent with one another. Use when the user wants to revise a change's plan, fold new decisions into it, or reconcile its artifacts after an edit. Never edits code.
openspec-verify-change
Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.