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 Qiao-920/claude-desktop-cn --skill code-reviewgit clone --depth 1 https://github.com/Qiao-920/claude-desktop-cnWrote 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/qiao-920/claude-desktop-cn/code-review)<a href="https://agentmods.dev/skills/qiao-920/claude-desktop-cn/code-review"><img src="https://agentmods.dev/badge/skills/qiao-920/claude-desktop-cn/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/qiao-920/claude-desktop-cn/code-review"><img src="https://agentmods.dev/badge/skills/qiao-920/claude-desktop-cn/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.00036 | $0.00429 |
| Opus 5.5 | $0.00014 | $0.00172 |
| Sonnet 5.5 | $0.00007 | $0.00086 |
| Haiku 4.5 | $0.00004 | $0.00043 |
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.
The source is not reproduced here
A licence we could not identify
The repository carries a LICENSE file, but it is custom or dual enough that GitHub cannot name it and neither can this catalogue. Unknown terms are not permission, so the body is not copied here. Read the licence at the source and decide for yourself.
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 · 60 lines · 36 tokens per session scan A 20060bd42e0e
code-review is a skill published in the GitHub repository Qiao-920/claude-desktop-cn (267 stars, last pushed 4mo ago), with no licence file. It adds 36 tokens to every session and 429 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
code-review
Systematic code review patterns covering security, performance, maintainability, correctness, and testing — with severity levels, structured feedback guidance, review process, and anti-patterns to avoid. Use when reviewing PRs, establishing review standards, or improving review quality.
code-review-specialist
A code-review guide for checking software changes for security, speed, and overall quality.
liveagent-code-review
Review an open GitHub pull request or the current local branch and working tree with parallel, independent reviewers and evidence-based validation. Use when the user asks for code review, invokes the Code Review action from Git Review, or explicitly mentions this skill.
nightly-audit-engineer-getting-started
A first-conversation guide for setting up a code-audit assistant. A code audit is a focused review of source code for defects or risky behavior, with the needed repository, scope, concerns, permissions, and schedule clarified first.
nightly-audit-engineer-ops
A workflow for reviewing code for reproducible quality problems and recording the evidence behind each finding. It follows data through inputs, permissions, storage, asynchronous work, and recovery, then suggests the smallest authorized fix.
engineer-bot-evidence
A local checker for confirming that delivery checks and supporting evidence belong to the current software version. It does not contact Git, continuous-integration systems, or the internet.