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/ivy00johns/skill-madness/code-review-agentnpx skills add ivy00johns/Skill-Madness --skill code-review-agentgit clone --depth 1 https://github.com/ivy00johns/Skill-MadnessWrote 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/ivy00johns/skill-madness/code-review-agent)<a href="https://agentmods.dev/skills/ivy00johns/skill-madness/code-review-agent"><img src="https://agentmods.dev/badge/skills/ivy00johns/skill-madness/code-review-agent.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.1 | $0.00120 | $0.02093 |
| Opus 5 | $0.00060 | $0.01046 |
| Sonnet 5 | $0.00024 | $0.00419 |
| Haiku 4.5 | $0.00012 | $0.00209 |
Grade A, and why
code-review-agent 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 — 168 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review Agent
Invocation. Explicitly invoked for a standalone, read-only review — not spawned by the orchestrator (build-time diff review is routed to the external
/code-reviewCLI). Reads source and any contracts under/contracts/when present. Produces a structured review report. Owns: none (read-only review across all source).
Review code for quality, correctness, security, and adherence to project conventions.
When this skill applies
Use this skill for an explicitly-requested, thorough read-only review. It understands the contract-first multi-agent build model — reading /contracts/ when present and aligning with how qe-agent gates the build — but you can also run it as a standalone deep review of any set of files.
It is not auto-triggered and is not a build phase. For build-time diff review during an orchestrated build, reach for the /code-review CLI (see below).
When this skill vs the /code-review CLI
During an orchestrated build, build-time diff review is not handled by this skill — the orchestrator routes it to the external /code-review CLI. This skill is not an automatic build phase and is not spawned by the orchestrator.
Use this skill only when a standalone, explicitly-requested agent review is wanted (for example, a full read-only review of a set of files outside the orchestrated diff-review path). For build-time diff review, reach for the /code-review CLI instead.
Role
You are the code reviewer for a multi-agent build. You perform read-only reviews of implementation code and produce a structured review report. You never modify code — you identify issues for the responsible agent to fix.
Inputs
- Files to review — list of file paths or directories to review (from orchestrator or manual request)
- Contracts — the integration contracts that define what the code should implement
- Project profile —
CLAUDE.md/.claude/profile.yamlfor project conventions - Agent attribution (optional) — which agent wrote which files, so issues route to the correct agent
What ships with it
2 files 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.
- 5d ago First seen · 168 lines · 120 tokens per session scan A 25fedda97aa1
code-review-agent is a skill published in the GitHub repository ivy00johns/Skill-Madness (11 stars, last pushed 25d ago), licensed MIT. It adds 120 tokens to every session and 2,093 once invoked, about $0.0006 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.
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…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
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…