preflight

preflight is a skill for Claude Code, Codex from nimble-giant/nimble-mold. It costs 50 tokens per session (678 once invoked), scanned A, original, Apache-2.0.

A planning step for software tasks that checks whether the work is clear, valuable, small, and testable. It also writes BDD acceptance criteria, meaning requirements in Given/When/Then form, and sketches the architecture before coding.

In plain words
What is it for?
Use it when scoping a new feature, planning an issue, or preparing a small development sprint before writing code.
Why use it?
It exposes unclear requirements and oversized tasks before implementation starts. This gives the developer and coding agent a shared description of what should be built and how success will be checked.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it when scoping a new feature, planning an issue, or preparing a small development sprint before writing code.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/nimble-giant/nimble-mold/preflight
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.

Any agent
npx skills add nimble-giant/nimble-mold --skill preflight
Clone the repo
git clone --depth 1 https://github.com/nimble-giant/nimble-mold

Made for: Claude Code, Codex.

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

agentmods badge for preflight

README.md
[![agentmods](https://agentmods.dev/badge/skills/nimble-giant/nimble-mold/preflight.svg)](https://agentmods.dev/skills/nimble-giant/nimble-mold/preflight)
Your own site
<a href="https://agentmods.dev/skills/nimble-giant/nimble-mold/preflight"><img src="https://agentmods.dev/badge/skills/nimble-giant/nimble-mold/preflight.svg" alt="Measured on agentmods" height="20"></a>
Per session 50 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 678 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.00050 $0.00678
Opus 5 $0.00025 $0.00339
Sonnet 5 $0.00010 $0.00136
Haiku 4.5 $0.00005 $0.00068

Measured 8d ago against content hash c09bdf696364, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, 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 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.

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.

skills/preflight/SKILL.md · 104 lines

How it starts

The opening of the file, as written. The whole thing — 104 lines — stays where its author put it; the contents beside it link to each section on GitHub.

preflight

Run pre-flight planning for a new task or mini-sprint.

Usage

/preflight
/preflight <issue-number>

Description

Executes the Pre-Flight Planning ceremony to ensure proper understanding and alignment before starting implementation.

{{- if .agent.plan_mode.enabled }} Important: When this command is invoked, immediately {{agent.plan_mode.enter}} to properly analyze and plan the task before any implementation begins.

Steps

First: {{agent.plan_mode.enter}} to properly analyze the task. This ensures thoughtful planning before implementation. {{- else }} Important: When this command is invoked, analyze and plan the task before any implementation begins. Present the analysis for user review.

Steps

First: Analyze the task thoroughly. This ensures thoughtful planning before implementation. {{- end }}

  1. Read & Clarify

    • Read the issue aloud
    • Capture domain language and user intent
    • Identify key requirements
  2. INVEST Check Evaluate the task against INVEST criteria:

    • Independent
    • Negotiable
    • Valuable
    • Estimable
    • Small
    • Testable
  3. Acceptance Criteria

    • Express as BDD specs (Given/When/Then format)
    • Ensure measurable outcomes
    • Cover edge cases
  4. Design Sketch If helpful, propose a light design:

    • Mermaid diagram for architecture
    • Bullet points for data flow
    • Test strategy outline
  5. Go/No-Go Decision

    • Present findings for approval
    • Request refinement if needed

Example Output

## Pre-Flight Analysis: Issue #123

### INVEST Evaluation
- ✅ Independent: Can be completed without other tickets
- ✅ Negotiable: Scope can be adjusted
- ✅ Valuable: Delivers user value
- ✅ Estimable: ~2 days effort
- ✅ Small: Fits in one sprint
- ✅ Testable: Clear pass/fail criteria

### Acceptance Criteria
```gherkin
Given a user has admin privileges
When they navigate to the settings page
Then they should see the "Export Data" button

Read the full file on GitHub · 104 lines

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. 8d ago First seen · 104 lines · 50 tokens per session scan A c09bdf696364

Subscribe to this mod's changes

preflight is a skill published in the GitHub repository nimble-giant/nimble-mold (2 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 50 tokens to every session and 678 once invoked, about $0.0003 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.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens