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.
git clone --depth 1 https://github.com/nitinjain999/platform-skillsWrote 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/commands/nitinjain999/platform-skills/preflight)<a href="https://agentmods.dev/commands/nitinjain999/platform-skills/preflight"><img src="https://agentmods.dev/badge/commands/nitinjain999/platform-skills/preflight.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.00123 | $0.07263 |
| Opus 5 | $0.00062 | $0.03632 |
| Sonnet 5 | $0.00025 | $0.01453 |
| Haiku 4.5 | $0.00012 | $0.00726 |
Grade C, and why
preflight scanned grade C 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 codehighSupply chain
curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.
- No `curl | bash` Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- No `curl | bash` How it starts
The opening of the file, as written. The whole thing — 634 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a senior platform engineer performing a production-readiness preflight check before a deployment or merge.
Input: $ARGUMENTS
Step 0 — Flags (parsed before Step 1)
Scan $ARGUMENTS for flags before determining scope. Strip them from the string before it is used as a path or pasted content in Step 1.
| Flag | Effect | Interview question it answers |
|---|---|---|
--env prod|staging|dev |
Sets environment | Q1 |
--focus security|correctness|ops|deprecations|all |
Sets focus scope | Q3 |
--bot |
Sets output format to Bot | Q4 |
--json |
Sets output format to JSON (see Step 8) | Q4 |
--changed-only[=<ref>] |
Restricts folder-mode discovery to files changed vs <ref> |
N/A — modifies Step 3 discovery, not an interview answer |
--no-interview |
Skips all remaining interview questions; unanswered ones take documented defaults | Q1, Q2, Q3, Q4 |
Rule: any question already answered by a flag is skipped in Step 2. If every question ends up answered — via flags, or because --no-interview supplies defaults for the rest — skip the interview entirely and proceed straight to Step 3. Q2 ("what is this change doing?") has no flag; under --no-interview it is simply omitted, and blast-radius/intent-matching findings that depend on it are marked Not verified with a note that intent capture was skipped, rather than guessed at.
--bot and --json select different output formats for the same Q4. If both are passed, --json takes precedence and silently wins — no warning is printed, since correctness of automated parsing matters more than a flag-conflict notice a CI author would notice from their own command line anyway.
Step 1 — Determine scope
Parse $ARGUMENTS to decide the mode:
| Input | Mode |
|---|---|
A directory path (e.g. ./k8s/, releases/my-app/) |
Folder mode — discover and check all files |
A glob (e.g. *.yaml, terraform/*.tf) |
Folder mode — check all matching files |
| A single file path or pasted content | Single-file mode |
| Nothing | Ask: "What would you like to preflight? Paste a file, give a path, or name a directory." |
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 · 634 lines · 123 tokens per session scan C 60a052deb7b4
preflight is a command published in the GitHub repository nitinjain999/platform-skills (41 stars, last pushed yesterday), licensed Apache-2.0. It adds 123 tokens to every session and 7,263 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
sm-sail
Command "sm-sail" from ScienceIsNeato/slop-mop, covering /sm-sail — drive a pr to green, autonomously, the loop, when sail parks on review threads, when to stop before "pr ready" — only two reasons and expect convergence, not one pass.
sm-buff
You usually don't run buff directly — run sm sail. sm sail drives the whole PR to green and calls buff watch / triage for you, stopping only when it needs you to act (see /sm-sail). Reach for sm buff here only for surgical work: inspecting a specific failure, or resolving a single review thread when sail has parked on…
devops
DevOps and infrastructure with Masao (CI/CD, Docker, cloud).
aw-author
Author, validate, or improve GitHub Agentic Workflow (gh-aw) markdown files.
sparc-devops
🚀 DevOps - You are the DevOps automation and infrastructure specialist responsible for deploying, managing, ...
review-before-deploy
Execute comprehensive pre-deployment review using code-review-agent with all relevant platform agents. Run complete deployment readiness checklist: verify all tests pass (unit, integration, E2E), security audit clean (no Critical/High issues), performance benchmarks met (Lighthouse > 90), TypeScript compilation…