Irrlicht: Skill for Claude Code

.claude/skills/ir:code-review/SKILL.md

ir:code-review is a skill for Claude Code from ingo-eichhorst/Irrlicht. It costs 152 tokens per session (2,208 once invoked), scanned A, original, MIT.

A repository-aware review of the changes in a Git working diff. A Git diff is the record of code added, changed, or removed since a chosen starting point.

In plain words
What is it for?
Reviewing local changes at different effort levels, checking repository conventions, verifying suspected problems, and recommending a human review for large or risky changes.
Why use it?
It looks for defects in the actual change and checks the project's own rules, while reporting the most serious findings first.

Skill for Claude Code

Written for Claude Code: installed under .claude/. Also seen: mentions subagents; mentions AGENTS.md.

This is ingo-eichhorst/Irrlicht's own configuration. It tells Claude Code how to work on Irrlicht itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything Irrlicht configures →

Reuse

Borrowing it

Nothing to install: this file belongs to ingo-eichhorst/Irrlicht. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/ingo-eichhorst/Irrlicht/main/.claude/skills/ir:code-review/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/ingo-eichhorst/Irrlicht

Made for: Claude Code.

Wrote 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.

agentmods badge for ir:code-review

README.md
[![agentmods](https://agentmods.dev/badge/skills/ingo-eichhorst/irrlicht/ir-code-review.svg)](https://agentmods.dev/skills/ingo-eichhorst/irrlicht/ir-code-review)
Your own site
<a href="https://agentmods.dev/skills/ingo-eichhorst/irrlicht/ir-code-review"><img src="https://agentmods.dev/badge/skills/ingo-eichhorst/irrlicht/ir-code-review.svg" alt="Measured on agentmods" height="20"></a>
Per session 152 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,208 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00152 $0.02208
Opus 5 $0.00076 $0.01104
Sonnet 5 $0.00030 $0.00442
Haiku 4.5 $0.00015 $0.00221

Measured yesterday against content hash 9366bb0dc45d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-06, from the pricing page.

Security

Grade A, and why

ir: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 yesterday.

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.

.claude/skills/ir:code-review/SKILL.md · 163 lines

How it starts

The opening of the file, as written. The whole thing — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Review the Working Diff

/ir:code-review [effort] [base]
Argument Values Default
effort low · medium · high · xhigh · max medium
base any git diff spec origin/main...HEAD

Both are positional and both optional: /ir:code-review, /ir:code-review high, and /ir:code-review low origin/main...HEAD are all valid. A bare effort word is an effort, never a PR number — this skill reviews a local diff and never takes a PR argument.

Why this skill exists

The built-in /code-review is marked disable-model-invocation: the Skill tool refuses it and it cannot be reached from Bash either. It is a human-triggered path. That left ir:exec's review gate unrunnable (#1205), so this is the repo's own reviewer — same job, agent-invocable, and aware of conventions in AGENTS.md that a general-purpose reviewer wouldn't check.

It is not a replacement for the real thing. For a large or risky diff, a human running /code-review <tier> origin/main...HEAD — or /code-review ultra for the cloud multi-agent pass — is still the stronger review, and recommending that is a legitimate outcome of this skill.

1 · Resolve the diff

git fetch origin main                      # refresh the base before diffing
git diff --stat <base>                     # scope
git diff <base>                            # the review surface

This skill already defaults to origin/main...HEAD. Keep it — inside a worktree, both of the defaults you'd otherwise reach for by hand mislead: the local main ref is stale (never updated when other PRs merge, so main...HEAD drags in already-merged hunks), and once the branch has been pushed with git push -u, @{upstream}...HEAD is ~empty (upstream now points at the pushed branch, so it reviews nothing). origin/main...HEAD after a fetch is the honest surface.

Review only what the diff changed, plus whatever the change puts at risk. An unrelated pre-existing wart is not a finding.

Read the full file on GitHub · 163 lines

Changes

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.

  1. yesterday Changed · -3 tokens per session 9366bb0dc45d
  2. 6d ago First seen · 163 lines · 155 tokens per session scan A c7f73a023b8c

Subscribe to this mod's changes

ir:code-review is a skill published in the GitHub repository ingo-eichhorst/Irrlicht (97 stars, last pushed today), licensed MIT. It adds 152 tokens to every session and 2,208 once invoked, about $0.0008 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

microsoft/vscode · 72 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

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…

vercel/next.js · 95 tokens