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 davidleitw/xreview --skill reviewgit clone --depth 1 https://github.com/davidleitw/xreviewWrote 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/davidleitw/xreview/review)<a href="https://agentmods.dev/skills/davidleitw/xreview/review"><img src="https://agentmods.dev/badge/skills/davidleitw/xreview/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.1 | $0.00122 | $0.02583 |
| Opus 5 | $0.00061 | $0.01291 |
| Sonnet 5 | $0.00024 | $0.00517 |
| Haiku 4.5 | $0.00012 | $0.00258 |
Grade B, and why
xreview scanned grade B with 2 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 8d 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.
Downloads and executes remote codemediumSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
b. If yes: run `curl -fsSL https://raw.githubusercontent.com/davidleitw/xreview/master/scripts/install.sh | bash` Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
allowed-tools: Bash(xreview *), Bash(curl *), Bash(which *), AskUserQuestion, Read, Write, Skill This is a copy
100% identical to xreview — 13 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 251 lines — stays where its author put it; the contents beside it link to each section on GitHub.
xreview - Agent-Native Code Review
Supported Languages for --language
| Key | Language |
|---|---|
cpp |
C++ |
go |
Go |
If review targets are written in a supported language, add --language <key>.
If unsure or mixed languages, omit --language — xreview falls back to general-purpose review.
Only use keys from the table above.
Step 0: Preflight
Run: xreview preflight
This single command checks everything: xreview version, codex installation, API key.
Parse the XML output:
- If status="success": proceed to Step 1.
- If status="error": show the user the error message from the tag. Relay it in natural language and suggest how to fix it. Stop.
If xreview itself is not found (which xreview fails):
a. Ask the user "xreview is not installed. Install it now? (y/n)"
b. If yes: run curl -fsSL https://raw.githubusercontent.com/davidleitw/xreview/master/scripts/install.sh | bash
then re-run preflight.
c. If install fails: tell the user to check https://github.com/davidleitw/xreview/releases. Stop.
Step 1: Determine review targets and assemble context
Two review modes — pick the one that fits:
Mode A: Review uncommitted changes (--git-uncommitted)
Use when reviewing what's about to be committed. Codex will run git diff
to see the changes itself.
Mode B: Review specific files (--files)
Use when:
- Reviewing a single file's quality (not tied to a git change)
- Reviewing a flow/feature that spans multiple files
- The user specifies which files to look at
- You just completed a plan with specific files changed
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.
- 8d ago First seen · 251 lines · 122 tokens per session scan B 9a21b413583e
xreview is a skill published in the GitHub repository davidleitw/xreview (12 stars, last pushed 5mo ago), licensed MIT. It adds 122 tokens to every session and 2,583 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it B with 2 findings (downloads and executes remote code, makes network calls). It is 100% identical to xreview, differing in 13 lines, and is treated as a copy.
Other skills, from other repositories
gemini
Cross-model second opinion from Google Gemini — a different AI reviewing the same changes, with deep Google ecosystem knowledge. Three modes: review (pass/fail gate for Google Ads campaigns, SEO metadata, or code), challenge (adversarial stress-test that tries to break your changes), and consult (open Q&A with Gemini…
audit
Project health audit and health check — architecture, performance, tests, dependencies, code quality. Use when assessing overall project health, before releases, or after refactors.
phx-pr-review
Address feedback left on a GitHub pull request: fetch unresolved review threads, make agreed Elixir/Phoenix code fixes, reply, and resolve. Use for a PR URL/number or reviewer comments. NOT for pre-PR review, findings triage, or CI monitoring.
boundaries
Analyze Phoenix context boundaries and module coupling via mix xref. Use when checking cross-context calls, validating dependencies, before splitting modules, or reviewing architecture.
challenge
Challenge mode reviews - rigorous questioning before approving changes. Use when you want thorough scrutiny of Ecto changes, LiveView events, OTP designs, or PR readiness.
triage
Triage review findings interactively — approve, skip, or prioritize each issue. Use after /phx:review to filter findings before fixing.