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 sonichi/sutando --skill review-preflightgit clone --depth 1 https://github.com/sonichi/sutandoWrote 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/sonichi/sutando/review-preflight)<a href="https://agentmods.dev/skills/sonichi/sutando/review-preflight"><img src="https://agentmods.dev/badge/skills/sonichi/sutando/review-preflight.svg" alt="Measured on agentmods" 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.00045 | $0.00318 |
| Opus 5 | $0.00023 | $0.00159 |
| Sonnet 5 | $0.00009 | $0.00064 |
| Haiku 4.5 | $0.00005 | $0.00032 |
Grade A, and why
review-preflight 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 2d 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.
What it actually says
review-preflight
Two tools, invoked by path; neither is a boot dependency of the core.
python3 skills/review-preflight/scripts/review-preflight.py <PR> # run before reviewing; reads <repo>/REVIEW.md
python3 skills/review-preflight/scripts/ci-triage.py <PR> [--repo o/n] # a red check is a pointer into the record: search its SUBJECT, not its name
review-preflight.py resolves the repo root via git rev-parse --show-toplevel, falling back to three
levels above its own file. ci-triage.py is advisory (exit 0), and is the module review-preflight will
fold in so a red check maps to a filed issue on every preflight run.
Moved here from scripts/ on the owner's decision (2026-09-04: "both review-preflight and ci-triage
don't belong to scripts/"); scripts/review-preflight.py and scripts/ci-triage.py remain as
two-line exec shims for one release so external callers (the pr-triage skill, peers' notes) keep
working until they are repointed.
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.
- 2d ago First seen · 24 lines · 45 tokens per session scan A 98444867fbe2
review-preflight is a skill published in the GitHub repository sonichi/sutando (393 stars, last pushed today), licensed MIT. It adds 45 tokens to every session and 318 once invoked, about $0.0002 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-09-05.
Other skills, from other repositories
github
Full GitHub CLI control — issues, PRs, code reviews, repo management. Uses gh CLI with auth detection, rate limiting, and templates. Triggers on: github, issue, pull request, PR, code review, repo, branch, label, assignee, milestone, release, workflow, actions.
twin-pr-triage
Scan open pull requests, assess risk and complexity, and build a prioritized review queue. Used by digital twin personas to reduce PR review cognitive load.
vellum-github-app-setup
Create and configure a GitHub App so the assistant can push commits, open PRs, and comment under its own bot identity. Use when the user wants the assistant to have its own GitHub identity, or when setting up git push access for the first time.
ship-pr
Ship one pull request, monitor hosted CI and review feedback, follow PR policy, and request authorization before merging and cleaning up.
repo-audit
Audit a repository or prepare it for an open-source release. Audit mode reports whether the README matches the code and whether stated rules are actually enforced; launch mode walks a repo to release-ready with opt-in checklist packs and README templates. Use when asked to "audit this repo," "is this repo ready to go…
github
GitHub integration — repos, issues, pull requests, branches, CI/Actions, code search, releases, gists, collaborators, labels, milestones, reviews, notifications, stars, forks, and more via the GitHub API.