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 ithinkihaveacat/dotfiles --skill agent-reviewgit clone --depth 1 https://github.com/ithinkihaveacat/dotfilesWrote 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/ithinkihaveacat/dotfiles/agent-review)<a href="https://agentmods.dev/skills/ithinkihaveacat/dotfiles/agent-review"><img src="https://agentmods.dev/badge/skills/ithinkihaveacat/dotfiles/agent-review.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/ithinkihaveacat/dotfiles/agent-review"><img src="https://agentmods.dev/badge/skills/ithinkihaveacat/dotfiles/agent-review.svg?style=web" alt="Reviewed on agentmods" width="80" height="15"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to high
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 →
- high Excessive Agency · line 56 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
- high Excessive Agency · line 57 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
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.00091 | $0.01139 |
| Opus 5 | $0.00046 | $0.00570 |
| Sonnet 5 | $0.00018 | $0.00228 |
| Haiku 4.5 | $0.00009 | $0.00114 |
Grade A, and why
agent-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 9d 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Review
Review changes independently and return only defects that the author would likely fix. Treat findings as claims that need evidence, not suggestions to improve code in general.
Choose the execution role
Determine which role this invocation has before doing anything else:
- Reviewer session: The current agent was asked to review the repository, or the prompt says this is a synthesized reviewer session. Perform the workflow below yourself. Do not launch another agent.
- Delegating session: The user asked to obtain an independent review from a
named CLI agent. Run
scripts/review-with-agentfrom this skill. The launcher uses native review commands where possible and explicitly invokes this skill for synthesized fallbacks.
Native review commands are process entry points, not tools a reviewer session must recursively call. Do not launch a second copy of the current agent merely because its CLI has native review support.
Delegate non-interactively
Run the launcher from the repository being reviewed:
scripts/review-with-agent --agent codex --base main
scripts/review-with-agent --agent claude --base main
scripts/review-with-agent --agent agy --commit HEAD
scripts/review-with-agent --agent agy --uncommitted
Paths beginning with scripts/ are relative to this skill directory. Use
--dry-run to inspect the selected command without starting an agent. Use
--synthesized to test the portable workflow even when a native route exists.
For a direct CLI invocation without the launcher, use the same distinction:
codex exec review --base main
claude -p "/code-review main...HEAD" --permission-mode dontAsk --no-session-persistence
agy --print "Use the installed agent-review skill to review the current branch against main. Perform the review yourself; do not delegate." --mode plan --sandbox
The launcher currently selects:
| Agent | Direct route | Synthesized fallback |
|---|---|---|
| Codex | Native base-to-HEAD, commit, and uncommitted review | Explicit $agent-review prompt |
| Claude | Local /code-review for a base range or single commit |
Explicit /agent-review prompt |
| agy | None | Explicit natural-language prompt |
What ships with it
5 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.
- 9d ago First seen · 117 lines · 91 tokens per session scan A 1e2592d95c80
agent-review is a skill published in the GitHub repository ithinkihaveacat/dotfiles (48 stars, last pushed yesterday), licensed Apache-2.0. It adds 91 tokens to every session and 1,139 once invoked, about $0.0005 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
GitHub PR comment fetcher
Easily query for open discussions and reviews on a pull request to help resolve them.
audit-architecture
Run an application-wide, read-only architecture audit that finds materially useful simplifications in a codebase's data structures, state representation, control flow, algorithms, and ownership boundaries. Fans out bounded read-only agents per subsystem, verifies every finding against the repo, and ranks results P0 to…
explain-changes
Explain how the code on the current branch works, as an HTML page opened in the browser, written so someone can understand the change and review it. Use when asked to explain a branch, explain these changes, walk me through this code, help me review this, or explain what an agent just did. Most useful when someone…
review-pr
Review and merge GitHub pull requests for Spatie packages. Use when asked to review a PR, review a pull request, merge a PR, or when given a GitHub PR URL to review. Also triggers on 'review this PR,' 'check this pull request,' 'merge this,' or '/review-pr'. Uses gh CLI for all GitHub operations.
review-code
Review all changed code against project conventions.
receiving-code-review
Use when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation.