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 natsukium/dotfiles --skill pi-reviewgit clone --depth 1 https://github.com/natsukium/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/natsukium/dotfiles/pi-review)<a href="https://agentmods.dev/skills/natsukium/dotfiles/pi-review"><img src="https://agentmods.dev/badge/skills/natsukium/dotfiles/pi-review/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/natsukium/dotfiles/pi-review"><img src="https://agentmods.dev/badge/skills/natsukium/dotfiles/pi-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00072 | $0.00984 |
| Opus 5.5 | $0.00029 | $0.00394 |
| Sonnet 5.5 | $0.00014 | $0.00197 |
| Haiku 4.5 | $0.00007 | $0.00098 |
Grade A, and why
pi-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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Reviews Through pi
Run a fresh pi process so the review does not inherit the calling conversation. The reviewer inspects the repository; the calling agent verifies findings and owns any revisions.
Models
| Model | Use for |
|---|---|
openai-codex/gpt-6.1-sol |
Adversarial design or diff review; final gate |
openai-codex/gpt-6-luna |
Early drafts, quick checks, and triage between sol rounds |
Use an explicitly requested model. Otherwise use luna for an early pass and sol for high-risk reasoning or the final pass.
Prepare the review
Write the change-specific information to a scratch file outside the repository:
# Review context
Target: <document or change>
Review range: <git diff, git diff --cached, or base...HEAD; omit for a document>
Revision context: <what changed and why>
Focus: <risks to examine>
Previous findings: <findings and claimed resolutions, or none>
Settled: <scope cuts and trade-offs the user already decided, or none>
Settled items are not findings: without them a reviewer re-flags every cut
as a gap in each round.
For a design, attach the document with --attach. For code, let pi inspect the
named Git range and surrounding source instead of copying the diff into the prompt.
The fixed review criteria and output format live in ./references/reviewer.md,
which the script passes itself.
Run the review
./scripts/pi-review launches pi detached from the calling shell and waits for it
in a separate step, so the review survives a caller whose shell is killed or
timed out. Run it from inside the target repository: it starts pi at the
repository root and refuses to start elsewhere.
<skill-directory>/scripts/pi-review start --out /abs/scratch/review-1 \
--context /abs/scratch/review-context.md [--attach /abs/path/design.md] [--model luna]
<skill-directory>/scripts/pi-review wait /abs/scratch/review-1
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.
- 9d ago Changed · +7 lines d0fd84d2b376
- 28d ago Changed 1ac22e941979
- 1mo ago Changed · +8 lines 2e9352c54bf8
- 1mo ago Changed 29367cf5e2c9
- 2mo ago First seen · 74 lines · 72 tokens per session scan A 5b597089b08c
pi-review is a skill published in the GitHub repository natsukium/dotfiles (106 stars, last pushed today), licensed CC0-1.0. It adds 72 tokens to every session and 984 once invoked, about $0.0003 per session on Opus 5.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
deep-research-team
This skill should be used when the user asks for "deep research", "research team", "comprehensive analysis", "research report", "investigate thoroughly", "compare X vs Y in depth", or needs synthesis across multiple sources with verification. It spawns a coordinated team of researcher agents across multiple rounds…
audit-permissions
This skill should be used when the user asks to "audit claude permissions", "audit permissions", "review local claude settings", "promote permissions to global", "clean up claude settings", "find permission patterns", or wants to identify project-local Claude Code permissions that should be added to global…
drift-check
Pre-PR advisory check for deviations from the project spec. Read-only analysis.
malo-find-skills
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
codebase-audit
Analyze a git repo's history to surface high-churn files, ownership risks, bug hotspots, momentum trends, and firefighting patterns. Use this skill whenever the user wants to understand a codebase, assess repo health, or orient themselves before reading code — even if they don't explicitly say "audit". Examples…
start
Enable auto TTS for this session.