A pre-flight check for a software project: it runs the appropriate validation checks for a chosen situation before work continues.

Use it before development, testing, releases, or other project work to determine which validators should run and whether the project is ready.

It helps reveal readiness problems early and gives follow-up guidance when a check fails.

check — Command for Claude Code by Data-Wise/craft

Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo

git clone --depth 1 https://github.com/Data-Wise/craft

agentmods

npx agentmods add commands/data-wise/craft/check

Made for: Claude Code.

Or install craft, the plugin that ships this one along with the rest of its 44 skills, 14 commands, 2 agents, 1 MCP server.

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/commands/data-wise/craft/check/github.svg)](https://agentmods.dev/commands/data-wise/craft/check)

Your own site

<a href="https://agentmods.dev/commands/data-wise/craft/check"><img src="https://agentmods.dev/badge/commands/data-wise/craft/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.

Your own site · 80×15

<a href="https://agentmods.dev/commands/data-wise/craft/check"><img src="https://agentmods.dev/badge/commands/data-wise/craft/check.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 8 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 2,826 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.00008	$0.02826
Opus 5.5	$0.00003	$0.01130
Sonnet 5.5	$0.00002	$0.00565
Haiku 4.5	$0.00001	$0.00283

Measured 1mo ago against content hash a4daf25b429c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

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.

commands/check.md · 316 lines

How it starts

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

/craft:check - Universal Pre-flight

This command is a thin(ner) shim. The canonical decision logic — which validators run for which --for context, mode budgets, follow-up routing on failure — lives in the preflight-check skill (skills/preflight-check/SKILL.md). This file keeps the parts that are invocation-specific and can't be deferred to skill-routing: the flag contract above, and the exact LLM-executable output format Claude must produce when this command runs (kept here per skills/code/command-skill-token-efficiency/SKILL.md's rule that anything the command always needs — even if skill-routing hasn't fired yet — stays in the command file).

Scope note: the pre-consolidation version of this command also carried full per-language project-detection walls (Python/Node/R/Go check lists), an extensive "community validator marketplace" section, and duplicated ASCII dry-run mockups for every mode/context combination. That's illustrative/aspirational content, not unique behavior — the skill's --for/mode tables already capture the decision logic, and .claude-plugin/skills/validation/*.md own the actual per-validator implementation. Dropped rather than ported; see the skill for anything that looks missing.

Usage

/craft:check                    # Quick validation
/craft:check thorough           # Deep validation
/craft:check --for commit       # Pre-commit checks
/craft:check --for pr           # Pre-PR checks
/craft:check --for release      # Pre-release checks
/craft:check --dry-run          # Preview checks
/craft:check -n                 # Preview checks
/craft:check --context              # Output session context only

Execution Behavior (MANDATORY)

When this command runs, Claude MUST follow these steps in order. Do NOT skip any step or proceed without showing the plan first.

Step 0: Show Check Plan

Before running ANY checks, display what will be checked:

Pre-flight Check Plan:
  Project: <project-name> (<project-type>)
  Mode: <mode>
  Branch: <current-branch>
  Guard: <protection-status>
  Context: <for-value or "general">

  Checks to run:
  1. <check-name> (<tool>)
  2. <check-name> (<tool>)
  ...
  N. <check-name> (<tool>)

Read the full file on GitHub · 316 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 First seen · 316 lines · 8 tokens per session scan A a4daf25b429c

Subscribe to this mod's changes

check is a command published in the GitHub repository Data-Wise/craft (4 stars, last pushed 7d ago), licensed MIT. It adds 8 tokens to every session and 2,826 once invoked, about $0.0000 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.

CI and CD Claude Code adhd-friendly architecture claude-plugin developer-toolkit

ci-sentinel

Daily autonomous classifier for failing PRs across your repos. Runs /ci-debug headless against every open PR with red required checks, posts the verdict as a collapsed PR comment, and appends to a per-repo .sentinel/ledger.jsonl. v1 is propose-don't-apply — NEVER auto-pushes a fix. Use when you're tired of /status…

yonatangross/orchestkit · 94 tokens

ci-debug

Diagnose a failing CI run against an 11-pattern playbook. Classifies the failure, cites the relevant memory entry, proposes the exact fix command — but NEVER applies without explicit user approval. Use when a specific PR check or GitHub Actions run failed and you want a diagnosis instead of speculation. Don't use for…

yonatangross/orchestkit · 92 tokens

check