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 skills add liatrio-labs/claude-code-gauntlet --skill build-review-mdgit clone --depth 1 https://github.com/liatrio-labs/claude-code-gauntletWrote 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/liatrio-labs/claude-code-gauntlet/build-review-md)<a href="https://agentmods.dev/skills/liatrio-labs/claude-code-gauntlet/build-review-md"><img src="https://agentmods.dev/badge/skills/liatrio-labs/claude-code-gauntlet/build-review-md/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/liatrio-labs/claude-code-gauntlet/build-review-md"><img src="https://agentmods.dev/badge/skills/liatrio-labs/claude-code-gauntlet/build-review-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 17 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00171 | $0.02783 |
| Opus 5 | $0.00086 | $0.01392 |
| Sonnet 5 | $0.00034 | $0.00557 |
| Haiku 4.5 | $0.00017 | $0.00278 |
Grade A, and why
build-review-md 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 — 222 lines — stays where its author put it; the contents beside it link to each section on GitHub.
REVIEW.md Builder
Guided wizard that creates a REVIEW.md configuration tailored to the repo's actual languages, frameworks, and priorities. Produces a root REVIEW.md and subdirectory configs only when the multi-stack test justifies them.
This skill produces configuration files, not code review. Do not run review agents or analyze code for bugs. Stay in configuration mode until exit.
Step 1: Detect
Scan the repository to understand what you are configuring. Do this silently — do not ask the user to describe their stack.
Languages — scan file extensions:
.ts,.tsx→ TypeScript/React.js,.jsx→ JavaScript.py→ Python.go→ Go.rs→ Rust.cs→ C#/.NET.java→ Java.rb→ Ruby.php→ PHP
Frameworks and runtimes — check for manifest files:
package.json→ Node/JS/TS ecosystem; readdependenciesanddevDependenciesfor React, Next.js, Vue, Express, NestJS, RTK Query, Zod, Vitest, Jestrequirements.txt/pyproject.toml/setup.py→ Python; check for Django, FastAPI, SQLAlchemy, pytestCargo.toml→ Rust; check for tokio, axum, sqlxgo.mod→ Go; check for gin, echo, gormpom.xml/build.gradle→ Java/Kotlin; check for Spring Boot, Hibernate*.csproj/*.sln→ .NET; check for ASP.NET Core, EF Core, xUnit, NUnitGemfile→ Ruby on Rails
Multi-stack / mono-repo detection — a repo is multi-stack when it contains multiple package manifest files in different subdirectories (e.g., frontend/package.json AND backend/*.csproj). Record the subdirectory paths.
Existing REVIEW.md — check whether a root REVIEW.md already exists. If it does, announce what you found and ask:
AskUserQuestion(
questions: [{
question: "A REVIEW.md already exists at the repo root. What would you like to do?",
header: "REVIEW.md",
multiSelect: false,
options: [
{ label: "Extend it (Recommended)", description: "Add rules to what's already there, keeping existing settings" },
{ label: "Start fresh", description: "Replace it with a newly generated REVIEW.md" },
{ label: "Cancel", description: "Keep the existing file unchanged and exit" }
]
}]
)
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 Changed · +2 lines e72e4bcb25fc
- 11d ago First seen · 220 lines · 171 tokens per session scan A 5ae2ac13947e
build-review-md is a skill published in the GitHub repository liatrio-labs/claude-code-gauntlet (12 stars, last pushed today), licensed Apache-2.0. It adds 171 tokens to every session and 2,783 once invoked, about $0.0009 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
doctor
Run a read-only hygiene + documentation audit on the current repo. TRIGGER when the user says "is this repo healthy", "check hygiene", "audit this repo" (when they mean inspect, not remediate), "what's drifted", "run doctor", "run a health check", "audit docs", "check for doc drift", "what's broken in this project"…
Refactor-Claim Audit リファクタ完了主張の検証
A review check for claims that a migration or refactor is complete, including claims about large reductions or unchanged behavior.
Logic Torturing 論理検証
A review method for testing the reasoning behind design choices and implementation decisions in a code change.
Self-Contradiction Detector 自己矛盾検出
A consistency check that compares written rules with the code or implementation next to them.
War Game 敵対的シミュレーション
A security review that examines code changes from the viewpoint of attackers, malicious users, insiders, or automated bots. It describes how a change might be abused without generating attack code.
Pre-mortem 失敗シナリオ分析
A review skill that imagines a future serious failure and works backward to find how it could happen. This approach is called a pre-mortem.