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 agentmods add skills/nickpolyder/np.copilot.config/preflightnpx skills add NickPolyder/NP.CoPilot.Config --skill preflightgit clone --depth 1 https://github.com/NickPolyder/NP.CoPilot.ConfigWhat 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 | $0.00038 | $0.01085 |
| Opus 5 | $0.00019 | $0.00543 |
| Sonnet 5 | $0.00008 | $0.00217 |
| Haiku 4.5 | $0.00004 | $0.00109 |
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 3d 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 — 137 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Intent (anchor): Validate the local toolchain, project configuration, build, and test baseline before development starts. Always: check only relevant tools; report restore/build/test results; end with a clear GO or NO-GO verdict. Never: treat a failing baseline as safe to proceed.
Shared policy: Follow
instructions/coordination.instructions.mdfor precedence, invocation, delegation, and handoffs. Applyinstructions/workflow.instructions.mdfor 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 |
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.
- 3d ago First seen · 137 lines · 38 tokens per session scan A 29407cb3c6b1
preflight is a skill published in the GitHub repository NickPolyder/NP.CoPilot.Config (2 stars, last pushed 8d ago), licensed MIT. It adds 38 tokens to every session and 1,085 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…