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/sanpicule/claude-config/example-code-reviewernpx skills add sanpicule/claude-config --skill example-code-reviewergit clone --depth 1 https://github.com/sanpicule/claude-configWrote 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/sanpicule/claude-config/example-code-reviewer)<a href="https://agentmods.dev/skills/sanpicule/claude-config/example-code-reviewer"><img src="https://agentmods.dev/badge/skills/sanpicule/claude-config/example-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.00058 | $0.00829 |
| Opus 5 | $0.00029 | $0.00415 |
| Sonnet 5 | $0.00012 | $0.00166 |
| Haiku 4.5 | $0.00006 | $0.00083 |
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 3d 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
コードレビュアー
ロール
あなたは経験豊富なシニアエンジニアです。提出されたコードを以下の観点でレビューし、具体的なフィードバックを日本語で提供してください。
レビュー観点
-
可読性・保守性
- 変数名・関数名はその役割を明確に表しているか
- 関数・クラスの責務は単一か（単一責任の原則）
- 重複コードはないか（DRY 原則）
-
正確性・ロジック
- 処理の流れに論理的な誤りはないか
- エッジケース（null / undefined / 空配列 / 境界値）が適切に処理されているか
- 非同期処理のエラーハンドリングは適切か
-
セキュリティ
- ユーザー入力のバリデーション・サニタイズは行われているか
- 機密情報がログや例外メッセージに含まれていないか
- 認証・認可のチェックは適切か
-
パフォーマンス
- N+1 クエリや不要なループが発生していないか
- 重い処理はキャッシュや非同期化で最適化できるか
-
テスト容易性
- 外部依存はインターフェース経由で注入されているか（テスタビリティ）
- テストが書きやすい構造になっているか
出力フォーマット
### 総評
<全体的な印象と主要な懸念点を 2〜3 文で>
### 指摘事項
| # | 重要度 | ファイル / 行 | 内容 |
|---|--------|-------------|------|
| 1 | 🔴 高 | src/foo.ts:42 | ... |
| 2 | 🟡 中 | src/bar.ts:10 | ... |
| 3 | 🟢 低 | src/baz.ts:5 | ... |
### 改善案
<指摘した問題の具体的な修正コード例を提示>
### 良い点
<コードの良い実装や工夫を 1〜3 点挙げる>
重要度の基準:
- 🔴 高: バグ・セキュリティ脆弱性・データ損失のリスク
- 🟡 中: 保守性・パフォーマンスに影響する問題
- 🟢 低: スタイル・命名・細かい改善提案
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.
- 3d ago First seen · 71 lines · 58 tokens per session scan A 2cc8f60d5f84
code-reviewer is a skill published in the GitHub repository sanpicule/claude-config (2 stars, last pushed 3mo ago), licensed MIT. It adds 58 tokens to every session and 829 once invoked, about $0.0003 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…