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/u9401066/nsforge-mcp/code-reviewernpx skills add u9401066/nsforge-mcp --skill code-reviewergit clone --depth 1 https://github.com/u9401066/nsforge-mcpWrote 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/u9401066/nsforge-mcp/code-reviewer)<a href="https://agentmods.dev/skills/u9401066/nsforge-mcp/code-reviewer"><img src="https://agentmods.dev/badge/skills/u9401066/nsforge-mcp/code-reviewer.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.00000 | $0.00386 |
| Opus 5 | $0.00000 | $0.00193 |
| Sonnet 5 | $0.00000 | $0.00077 |
| Haiku 4.5 | $0.00000 | $0.00039 |
Grade A, and why
code-reviewer 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 5d 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.
Copies of this mod
4 near-identical copies found in the catalogue:
- code-reviewer — 100% identical, 0 lines differ
- code-reviewer — 100% identical, 0 lines differ
- code-reviewer — 100% identical, 2 lines differ
- code-reviewer — 100% identical, 2 lines differ
What it actually says
程式碼審查技能
描述
對程式碼進行全面審查，檢查品質、安全性和最佳實踐。
觸發條件
- 「review 這段程式碼」
- 「檢查程式碼」
- 「code review」
審查項目
1. 程式碼品質
- 命名是否清晰
- 函數長度是否合理（建議 < 50 行）
- 是否遵循 DRY 原則
- 複雜度是否過高
2. 安全性
- SQL 注入風險
- XSS 漏洞
- 敏感資料暴露
- 權限檢查
3. 效能
- N+1 查詢問題
- 不必要的迴圈
- 記憶體洩漏風險
4. 可維護性
- 註解是否充足
- 錯誤處理是否完整
- 測試覆蓋率
輸出格式
## 審查結果
### ✅ 優點
- ...
### ⚠️ 建議改進
- [嚴重程度] 問題描述
- 位置：第 X 行
- 建議：...
### 📊 評分
- 品質：X/10
- 安全：X/10
- 效能：X/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.
- 5d ago First seen · 58 lines · 0 tokens per session scan A c214a3874212
code-reviewer is a skill published in the GitHub repository u9401066/nsforge-mcp (4 stars, last pushed 5d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 386 tokens. 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
vera-language
Write programs in the Vera programming language. Use when asked to write, edit, debug, or review Vera code (.vera files). Vera is a statically typed, purely functional language with algebraic effects, mandatory contracts, and typed slot references (@T.n) instead of variable names.
kverus-strip
Aggressively strip redundant proof code from a Verus codebase while keeping verification passing. Use when you want to slim down Verus proof bloat, simplify redundant proof asserts, or run postprocess cleanup without breaking verification.
kverus-review
Review uncommitted or recent Verus code changes for exec-code modifications, unnecessary == introductions, and verification issues. Use before committing to catch regressions in executable semantics, set reasoning, and proof quality.
kverus-run
Run the full Rust-to-Verus pipeline (migrate → spec → fix → eval → semantic audit → postprocess) in one command. Use when converting Rust code to verified Verus code end-to-end.
kverus-fix
Fix Verus verification errors by iterating minimal proof-preserving edits until verification succeeds. Use with an explicit target and verification command, or automatically discover the command and locate the target from fresh diagnostics when either input is unavailable.
kverus-semantic-audit
Compare original Rust source folders against migrated Verus code folders, identify executable-code differences that may change runtime semantics, and write per-file audit reports to an output folder. Use when checking whether Rust-to-Verus rewriting preserved executable behavior rather than merely verifying…