A readiness check for a software project before development starts. It checks the required tools, project settings, build, and existing tests, then gives a GO or NO-GO result.

Use it when starting work in an unfamiliar or newly cloned project. It helps verify the toolchain, configuration, build, and tests are ready.

It finds broken setup or an already-failing project before new changes make diagnosis harder. A test baseline is the known-good state used to detect later regressions.

preflight — Skill for Claude Code and Codex by NickPolyder

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 NickPolyder/NP.CoPilot.Config --skill preflight

Clone the repo

git clone --depth 1 https://github.com/NickPolyder/NP.CoPilot.Config

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/nickpolyder/np.copilot.config/preflight/github.svg)](https://agentmods.dev/skills/nickpolyder/np.copilot.config/preflight)

Your own site

<a href="https://agentmods.dev/skills/nickpolyder/np.copilot.config/preflight"><img src="https://agentmods.dev/badge/skills/nickpolyder/np.copilot.config/preflight/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/nickpolyder/np.copilot.config/preflight"><img src="https://agentmods.dev/badge/skills/nickpolyder/np.copilot.config/preflight.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 38 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,078 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.

Model	Per session	Once invoked
Fable 5.1	$0.00038	$0.01078
Opus 5.5	$0.00015	$0.00431
Sonnet 5.5	$0.00008	$0.00216
Haiku 4.5	$0.00004	$0.00108

Measured 1mo ago against content hash 636b91c5cf83, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, 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 1mo 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 · 136 lines

How it starts

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

Purpose

Shared policy: Follow instructions/coordination.instructions.md for precedence, invocation, delegation, and handoffs. Apply instructions/workflow.instructions.md for proportional work and verification.

You are running a preflight check to verify the environment is ready for development.

Your goals are to:

Validate toolchain — confirm required tools are installed and accessible.
Check project health — verify the project builds and tests pass.
Surface blockers early — catch configuration issues before work begins.
Produce a go/no-go — clear assessment with actionable fixes for any issues.

When to use this skill

Use this skill whenever:

Starting work on a new or unfamiliar project.
The user asks to "check my setup", "verify environment", or "preflight".
Before a major implementation effort to confirm baseline health.
After cloning a repo or switching branches.

Do not use this skill for:

Debugging specific build failures — investigate those directly.
CI/CD pipeline issues — those are a DevOps concern.

Checks

Run these checks in order. Report results as they complete.

1. Global Toolchain

Verify these tools are available (run the version command for each):

Tool	Check Command	Required
Git	`git --version`	Always
.NET SDK	`dotnet --version`	If .cs files exist
Node.js	`node --version`	If package.json exists
npm/pnpm/yarn	`npm --version` (or equivalent)	If package.json exists
PowerShell	`$PSVersionTable.PSVersion`	Always (Windows)
Docker	`docker --version`	Only if docker-compose.yml or Dockerfile exists

Skip tools that aren't relevant to the current project.

2. Project Configuration

Git status — clean working tree? Uncommitted changes?
Branch — which branch are we on? Is it up to date with remote?
Project contracts — read .github/instructions/project-config.instructions.md and relevant existing Copilot/AGENTS.md/CLAUDE.md/GEMINI.md contracts. Missing project-config alone is not unhealthy. If recommending templates, use the verified NP.CoPilot.Config source and preserve/reference existing capability declarations rather than introducing default-disabled conflicts.
Solution/project files — can you find .sln, .csproj, package.json, or equivalent entry points?

Read the full file on GitHub · 136 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.

1mo ago Changed · -1 lines 636b91c5cf83
1mo ago First seen · 137 lines · 38 tokens per session scan A 29407cb3c6b1

Subscribe to this mod's changes

preflight is a skill published in the GitHub repository NickPolyder/NP.CoPilot.Config (2 stars, last pushed 1mo ago), licensed MIT. It adds 38 tokens to every session and 1,078 once invoked, about $0.0002 per session on Opus 5.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.

Testing

research-engineer

An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.

davila7/claude-code-templates · 43 tokens

tika-eval-compare

Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".

apache/tika · 50 tokens

cua-driver

Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.

davidondrej/skills · 68 tokens

preflight