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 mirekondro/The-Pre-Flight-Check --skill pre-flight-checkgit clone --depth 1 https://github.com/mirekondro/The-Pre-Flight-CheckWrote 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/mirekondro/the-pre-flight-check/pre-flight-check)<a href="https://agentmods.dev/skills/mirekondro/the-pre-flight-check/pre-flight-check"><img src="https://agentmods.dev/badge/skills/mirekondro/the-pre-flight-check/pre-flight-check/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/mirekondro/the-pre-flight-check/pre-flight-check"><img src="https://agentmods.dev/badge/skills/mirekondro/the-pre-flight-check/pre-flight-check.svg" alt="Reviewed on agentmods" width="80" 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.00045 | $0.01468 |
| Opus 5 | $0.00023 | $0.00734 |
| Sonnet 5 | $0.00009 | $0.00294 |
| Haiku 4.5 | $0.00005 | $0.00147 |
Grade A, and why
pre-flight-check 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 11d 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pre-Flight Check
A mandatory, fail-fast quality gate. Runs Typecheck → Lint → Test → Security Audit sequentially via scripts/run-pipeline.py. The script auto-detects the project runtime (Node.js or Python) and exits with code 1 on the first failing stage, emitting a structured Markdown block you must parse.
When to invoke
Run this skill without being asked at every one of these checkpoints:
- Before announcing a task is "done" — any task involving code edits.
- Before staging, committing, or pushing any change.
- After applying a bug fix — to confirm the fix holds across all gates, not just the failing test.
- Before opening a PR or marking work ready for review.
If you are about to say "done", "fixed", "complete", "ready to commit", or similar — stop and run this skill first.
How to run
Execute from the repository root:
python .claude/skills/pre-flight-check/scripts/run-pipeline.py
The script writes a header per stage as it progresses, then emits one of:
### ✅ PRE-FLIGHT PASSED— exit0. Safe to proceed.### ❌ PRE-FLIGHT FAILURE: [STAGE_NAME]— exit1. Stop and fix.### ⚠️ PRE-FLIGHT SKIPPED: …— exit1. Runtime undetected or no stages resolved. Resolve tooling before proceeding.
Strict Fail-Fast Protocol
If the script outputs ### ❌ PRE-FLIGHT FAILURE: [STAGE_NAME], you are FORBIDDEN from:
- Declaring the task done.
- Committing, staging, or pushing any code.
- Switching to a different task, file, or feature.
- Suppressing the error (no
// @ts-ignore, no# noqa, noeslint-disable, nopytest.skip, no removing the failing test, no wideningignoreglobs). - Re-running the pipeline hoping for a flake. Failures are real until proven otherwise by a fix in source.
Your only permitted next action is to repair the specific error reported by the failing stage and re-run the pipeline. Continue this loop until you see ### ✅ PRE-FLIGHT PASSED.
Stage-specific repair rules
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.
- 11d ago First seen · 109 lines · 45 tokens per session scan A 0051d66961fa
pre-flight-check is a skill published in the GitHub repository mirekondro/The-Pre-Flight-Check (2 stars, last pushed 3mo ago), licensed MIT. It adds 45 tokens to every session and 1,468 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-08-31.
Other skills, from other repositories
e2e-testing
Guide for running end-to-end tests of the Qwen Code CLI, including headless mode, MCP server testing, and API traffic inspection. Use this skill whenever you need to verify CLI behavior with real model calls, reproduce user-reported bugs end-to-end, test MCP tool integrations, or inspect raw API request/response…
terminal-capture
Automates terminal UI screenshot testing for CLI commands. Applies when reviewing PRs that affect CLI output, testing slash commands (/about, /context, /auth, /export), generating visual documentation, or when 'terminal screenshot', 'CLI test', 'visual test', or 'terminal-capture' is mentioned.
tmux-real-user-testing
A real-user test workflow for Qwen Code's terminal interface, using tmux to drive the program and capture readable screen snapshots. tmux is a tool for running and observing terminal sessions.
agent-reproduce-align
Use after a Codex or Claude Code feature has been implemented in Qwen Code to run the selected reference agent and Qwen Code under the same scenario, capture HTTP and terminal traces, compare request bodies, tool/function schemas, outputs, and iterate until the reproduced behavior is close enough.
deflake
Stabilize a flaky test with a minimal, assertion-preserving fix — never by weakening or deleting the check.
safe-extraction
Apply when extracting code from a large monolith file into submodules. Covers barrel re-exports, internals DI seam proxy patterns, CI invariant allowlist updates, and cross-file test verification. Prevents CI failures, broken imports, and test regressions from code extraction.