preflight

A final code-quality check run before changes are committed to a code repository. A commit is a saved set of project changes in version control.

In plain words
What is it for?
Use it to review logic, asynchronous code, API changes, loading and error states, tests, naming, database rollbacks, financial calculations, and security findings with file-and-line references.
Why use it?
It catches edge cases, missing error handling, regressions, incomplete features, and changes that do not match the approved plan. A BLOCK result means the commit should stop until the issue is fixed.

Agent

Install

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.

agentmods
npx agentmods add agents/rune-kit/rune/preflight
Clone the repo
git clone --depth 1 https://github.com/Rune-kit/rune
Per session 35 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 389 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00035 $0.00389
Opus 5 $0.00017 $0.00195
Sonnet 5 $0.00007 $0.00078
Haiku 4.5 $0.00003 $0.00039

Measured yesterday against content hash 3624c75dd419, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

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 yesterday.

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.

agents/preflight.md · 30 lines

What it actually says

You are the preflight skill — Rune's last defense before code enters the repo.

Quick Reference

Workflow:

  1. Stage A — Spec Compliance — verify code matches approved plan (missing planned change = BLOCK, unplanned change = WARN)
  2. Logic Review — null/undefined crashes, async/await issues, boundary conditions, type coercions
  3. Error Handling — try/catch on async, no bare catches, fetch status checks, user-friendly errors
  4. Regression Check — identify dependents, check signature compatibility, flag untested impact
  5. Completeness — new API → validation schema, new component → loading + error states, new feature → tests
  6. Coherence — naming conventions, file organization, import patterns consistency
  7. Domain Quality Hooks — database rollback, API contract, legal, financial decimals
  8. Security Sub-Check — invoke sentinel, attach output
  9. Composite Score — (Logic×0.30) + (ErrorHandling×0.20) + (Completeness×0.20) + (Coherence×0.15) + (RegressionRisk×0.15)
  10. Verdict — PASS / WARN (must acknowledge each) / BLOCK (must fix)

Critical Rules:

  • Every finding MUST have file:line reference
  • "Happy path works" is insufficient — edge cases MUST be checked
  • Error messages must not leak internals (no stack traces to client)

Read skills/preflight/SKILL.md for the full specification including organization requirements.

Changes

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.

  1. yesterday First seen · 30 lines · 35 tokens per session scan A 3624c75dd419

Subscribe to this mod's changes

preflight is an agent published in the GitHub repository Rune-kit/rune (84 stars, last pushed 16d ago), licensed MIT. It adds 35 tokens to every session and 389 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-30.

Related

Other agents, from other repositories

polymath

Cross-disciplinary synthesis; spawns domain-specific subagents, synthesizes findings across domains, and produces integrated insights.

pjt222/agent-almanac · 25 tokens

insistir-reviewer

Cross-review agent for insistir multi-agent orchestration. Reviews another agent's implementation and sends structured findings to the lead. Read-only — cannot edit or write files. Can run verification commands (tests, typecheck, lint) via whitelisted Bash. Enforces quality without gatekeeping. Do NOT use directly …

JairoTorregrosa/jaiskills · 76 tokens

insistir-researcher

Research agent for insistir orchestration. Researches best practices, framework documentation, and codebase patterns. Read-only — cannot edit or write files. Do NOT use directly — spawned by insistir skill orchestration.

JairoTorregrosa/jaiskills · 50 tokens

insistir-learnings-researcher

Knowledge search agent for insistir multi-agent orchestration. Searches docs/solutions/ for past solutions relevant to a query using grep-first strategy with parallel keyword searches including synonyms. Read-only — cannot edit, write, or execute commands. Do NOT use directly — spawned by insistir skill orchestration.

JairoTorregrosa/jaiskills · 68 tokens

insistir-worker

Implementation agent for insistir multi-agent orchestration. Implements a task or applies review fixes, commits, reports to lead. Do NOT use directly — spawned by insistir skill orchestration.

JairoTorregrosa/jaiskills · 42 tokens

askit-explorer

Surveys a repository broadly and reports a structural map of its components and layout. Use when delegating broad read-only exploration - the bounded discovery role for answering what exists and how a repo is organized.

product-on-purpose/agent-skills-toolkit · 45 tokens