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 Data-Wise/craft --skill preflight-checkgit clone --depth 1 https://github.com/Data-Wise/craftWrote 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/data-wise/craft/preflight-check)<a href="https://agentmods.dev/skills/data-wise/craft/preflight-check"><img src="https://agentmods.dev/badge/skills/data-wise/craft/preflight-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/data-wise/craft/preflight-check"><img src="https://agentmods.dev/badge/skills/data-wise/craft/preflight-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.00100 | $0.02074 |
| Opus 5.5 | $0.00040 | $0.00830 |
| Sonnet 5.5 | $0.00020 | $0.00415 |
| Haiku 4.5 | $0.00010 | $0.00207 |
Grade A, and why
preflight-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 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.
How it starts
The opening of the file, as written. The whole thing — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pre-flight Check
Universal pre-flight validation across commit, PR, release, and deploy boundaries. Orchestrates the validator suite that lives under .claude-plugin/skills/validation/ and dispatches the right check set for the current context.
When to Use
- User asks "is this ready to commit / PR / release / deploy?"
- User says "pre-flight", "validate", "check readiness", or runs
/craft:check - Before staging a commit, opening a PR, or kicking off the release pipeline
- After a session of edits, to confirm nothing regressed
- When the user wants to scaffold a new custom validator (
gen-validatorflow)
Scope Boundary (Read This First)
This skill is broader than its siblings — understand the seams:
| Skill | Concern | Does NOT cover |
|---|---|---|
| preflight-check (this) | Cross-cutting validators: lint, tests, types, version sync, stale refs, link integrity, hook conflicts, CLAUDE.md health, docs staleness, badge URLs, formula desc, skill standards (release-gated) | Detection logic, release orchestration, guard rule editing |
project-detector (skills/ci/) |
Detect project type / build tool / test framework to recommend a CI template | Validation orchestration. It answers "what kind of project is this?" not "is it ready?" |
release (skills/release/) |
The full release pipeline (version bump → PR → merge → GitHub release → Homebrew → verify). Calls this skill internally for its Step 2 pre-flight gate | Standalone commit/PR validation |
guard-audit (skills/guard-audit/) |
Tune branch-guard.sh rules via .claude/branch-guard.json to reduce false positives |
Running checks. It edits guard config, doesn't validate the project |
Rule of thumb: if the user wants to run validators, use this skill. If they want to change which rules block them, route to guard-audit. If they want a release, route to release (which calls back into this skill).
Backing Commands
/craft:check— primary entry point; mode-aware, context-aware orchestrator
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.
- 1mo ago First seen · 133 lines · 100 tokens per session scan A 5ad202e5de58
preflight-check is a skill published in the GitHub repository Data-Wise/craft (4 stars, last pushed 9d ago), licensed MIT. It adds 100 tokens to every session and 2,074 once invoked, about $0.0004 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-09-03.
Other skills, from other repositories
swarm-migrate
Cross-repo migration swarm — one coordinator + N parallel subagents (one per target repo) that apply the same transformation, open PRs, wait for CI, and report back to a shared JSON ledger. Coordinator handles topology, conflict auto-rebase, and stop-on-novel-failure. Use when bumping a shared dependency, rolling out…
pdlc-ship
A software release workflow that runs tests, updates the version and change log, creates a Git tag, and starts CI/CD, the automated build and deployment process.
tfx-ship
A release workflow for publishing triflux versions through GitHub Releases, the npm package registry, and the Claude Code marketplace. It also supports version changes, dry runs, skipped tests, and no-publish runs.
wicked-garden-platform-gh-cli
Use when you need gh CLI patterns beyond the basics — debugging failed workflow runs, bulk PR operations, release automation, or repo health checks. Provides composable gh invocations for power users. NOT for simple git commands (use Bash) or GitLab (use the glab-cli skill). Use when: "debug the failed workflow run"…
wicked-garden-platform-glab-cli
Use when you need glab CLI patterns for GitLab — pipeline debugging, MR management, or release automation. Provides composable glab invocations for power users. NOT for GitHub (use the gh-cli skill) or simple git commands (use Bash).
quality-release
Use when thinking through, reviewing, changing, or verifying quality and release readiness: test strategy, test data, concurrency and failure testing, load and performance evidence, scalability, resource management, compression, release exceptions or waivers, cross-domain completion, and production-ready claims. For…