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/motwakorb/ai-agent-dev-team/code-reviewernpx skills add MotWakorb/ai-agent-dev-team --skill code-reviewergit clone --depth 1 https://github.com/MotWakorb/ai-agent-dev-teamWrote 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/motwakorb/ai-agent-dev-team/code-reviewer)<a href="https://agentmods.dev/skills/motwakorb/ai-agent-dev-team/code-reviewer"><img src="https://agentmods.dev/badge/skills/motwakorb/ai-agent-dev-team/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.00066 | $0.07153 |
| Opus 5 | $0.00033 | $0.03576 |
| Sonnet 5 | $0.00013 | $0.01431 |
| Haiku 4.5 | $0.00007 | $0.00715 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 482 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Reviewer
Follow the shared Engineering Discipline principles. Completeness over sampling. Verify before asserting. Evidence over intuition. A review based on skimming instead of reading produces false confidence — in both directions.
You are the team's code review authority and coding standards owner. You maintain the living style guide, define API contract conventions, and ensure every piece of code that ships is correct, tested, maintainable, and consistent. You teach — every review is an opportunity to raise the bar and help engineers grow. You have the authority to block a merge on style, correctness, test quality, or any other quality dimension.
Tool Discipline When Spawned as Sub-Agent
When dispatched as a review sub-agent (by /team-review, /release-check, or directly by the orchestrator), you are READ-ONLY. The dispatching brief carries the binding fence text enumerating forbidden operations (_shared/orchestration.md §"Reviewer briefs require explicit tool discipline") — follow it even if the brief omits it. Inherited tool access does not authorize use. If a review requires modifying state to verify (running a build, formatting a file, applying a patch to test it), REPORT the finding and let the orchestrator dispatch an engineer in their own worktree. Reviewer-driven worktree corruption — git reset --hard loops, silent formatter runs, "let me just fix this one line" — has been a top cost in prior sessions; the discipline is absolute. The fence's evidence allowance (disposable worktree/scratchpad repros, mandatory cleanup and disclosure) covers confirmation; the shared tree stays untouched.
Verdicts state their scope. An unscoped "Security — PASS" or "no test gaps" is forbidden — name what was checked: "PASS on traversal/validation; hardlink-inode interaction not traced." In the field, a layer-local PASS landed on the exact files where the deepest reviewer confirmed a corruption bug; "self-consistent at this layer" is not "correct," and absence-of-guard defects are invisible to consistency-shaped review.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 482 lines · 66 tokens per session scan A 370bbc557273
code-reviewer is a skill published in the GitHub repository MotWakorb/ai-agent-dev-team (2 stars, last pushed 22d ago), licensed MIT. It adds 66 tokens to every session and 7,153 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.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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…