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/jorgejie/ai_scaffold/code_reviewnpx skills add Jorgejie/ai_scaffold --skill code_reviewgit clone --depth 1 https://github.com/Jorgejie/ai_scaffoldWrote 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/jorgejie/ai_scaffold/code_review)<a href="https://agentmods.dev/skills/jorgejie/ai_scaffold/code_review"><img src="https://agentmods.dev/badge/skills/jorgejie/ai_scaffold/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.00007 | $0.01136 |
| Opus 5 | $0.00003 | $0.00568 |
| Sonnet 5 | $0.00001 | $0.00227 |
| Haiku 4.5 | $0.00001 | $0.00114 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
{{t "code_review.title"}}
{{t "code_review.trigger_title"}}
- {{t "code_review.trigger_1"}}
- {{t "code_review.trigger_2"}}
- {{t "code_review.trigger_3"}}
- {{t "code_review.trigger_4"}}
{{t "code_review.skip"}}
1 {{t "code_review.checklist_title"}}
1.1 {{t "code_review.fatal_title"}}
| # | Check | Method |
|---|---|---|
| 1 | {{t "code_review.fatal_row1"}} | |
| 2 | {{t "code_review.fatal_row2"}} | |
| 3 | {{t "code_review.fatal_row3"}} | |
| 4 | {{t "code_review.fatal_row4"}} | |
| 5 | {{t "code_review.fatal_row5"}} | |
| 6 | {{t "code_review.fatal_row6"}} | |
| {{PLATFORM_FATAL_CHECKS}} | ||
| {{#if HAS_NDK}} | ||
| F-NDK1 | {{t "code_review.fatal_ndk1"}} | |
| F-NDK2 | {{t "code_review.fatal_ndk2"}} | |
| F-NDK3 | {{t "code_review.fatal_ndk3"}} | |
| F-NDK4 | {{t "code_review.fatal_ndk4"}} | |
| F-NDK5 | {{t "code_review.fatal_ndk5"}} | |
| F-NDK6 | {{t "code_review.fatal_ndk6"}} | |
| {{/if}} |
1.2 {{t "code_review.warning_title"}}
| # | Check | Method |
|---|---|---|
| 7 | {{t "code_review.warning_row7"}} | |
| 8 | {{t "code_review.warning_row8"}} | |
| 9 | {{t "code_review.warning_row9"}} | |
| 10 | {{t "code_review.warning_row10"}} | |
| {{PLATFORM_WARNING_CHECKS}} | ||
| {{#if HAS_NDK}} | ||
| W-NDK1 | {{t "code_review.warning_ndk1"}} | |
| W-NDK2 | {{t "code_review.warning_ndk2"}} | |
| W-NDK3 | {{t "code_review.warning_ndk3"}} | |
| W-NDK4 | {{t "code_review.warning_ndk4"}} | |
| W-NDK5 | {{t "code_review.warning_ndk5"}} | |
| {{/if}} |
1.3 {{t "code_review.suggestion_title"}}
| # | Check | Method |
|---|---|---|
| 11 | {{t "code_review.suggestion_row11"}} | |
| 12 | {{t "code_review.suggestion_row12"}} | |
| 13 | {{t "code_review.suggestion_row13"}} | |
| 14 | {{t "code_review.suggestion_row14"}} | |
| {{PLATFORM_SUGGESTION_CHECKS}} | ||
| {{#if HAS_NDK}} | ||
| S-NDK1 | {{t "code_review.suggestion_ndk1"}} | |
| S-NDK2 | {{t "code_review.suggestion_ndk2"}} | |
| S-NDK3 | {{t "code_review.suggestion_ndk3"}} | |
| S-NDK4 | {{t "code_review.suggestion_ndk4"}} | |
| S-NDK5 | {{t "code_review.suggestion_ndk5"}} | |
| {{/if}} |
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 · 118 lines · 7 tokens per session scan A da77632abdaa
code_review is a skill published in the GitHub repository Jorgejie/ai_scaffold (52 stars, last pushed 24d ago), licensed MIT. It adds 7 tokens to every session and 1,136 once invoked, about $0.0000 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
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…