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/data-wise/craft/drive-enginenpx skills add Data-Wise/craft --skill drive-enginegit clone --depth 1 https://github.com/Data-Wise/craftWhat 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.00079 | $0.00586 |
| Opus 5 | $0.00039 | $0.00293 |
| Sonnet 5 | $0.00016 | $0.00117 |
| Haiku 4.5 | $0.00008 | $0.00059 |
Grade A, and why
drive-engine 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 yesterday.
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.
What it actually says
Drive Engine
The reusable execution body behind /craft:orch:drive. The command
owns condition synthesis and gating; this skill owns the work.
Responsibilities
- Resolve phases — if an
ORCHESTRATE-*.mdexists in the worktree root, parse its phases and file-scopes. If not, derive phases directly from the SPEC's## Phase/## Increment/task-list sections. An ORCHESTRATE file is preferred when present but never required. - Dispatch — per turn, launch
--agents N(default 1) file-scoped subagents, one per pending wave item, each scoped to its files only. Keep the transcript linear whenN == 1so the/goalevaluator can read it. - Real verify gate — when the
/goalcondition clears, run the project's actual verification (auto-detected, see table) and treat its exit status as the authoritative "done". A green transcript is NOT sufficient; the command must actually run.
Phase resolution
Look for, in order: worktree ORCHESTRATE-*.md → SPEC ## Phase N /
## Increment N headings → top-level numbered task list. Emit a wave list
of {phase, files[], tasks[]}.
Verify-command auto-detection
See ../references/verify-gate-detection.md for the
full detection table and how to use it. Always pair with git status --short to confirm a clean,
committed tree.
Outputs
A structured verify result: { command, exit_code, passed: bool, summary }.
On passed: true, the caller stops at verified-green and prints the
gh pr create command — this skill never opens a PR.
Not this skill's job
The #NNN issue-premise pre-filter (does the spec cite an open issue? if
so, run /craft:git:issue-check <N> and surface the verdict) lives in
/craft:orch:drive's own Step 2, not here — it's part of the command's
gating responsibility, run once before any dispatch begins. It never
blocks and never runs unless a citation is found.
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.
- yesterday First seen · 51 lines · 79 tokens per session scan A f591a1419511
drive-engine is a skill published in the GitHub repository Data-Wise/craft (4 stars, last pushed 16d ago), licensed MIT. It adds 79 tokens to every session and 586 once invoked, about $0.0004 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
github-actions-workflow
Scaffolds or audits a GitHub Actions CI/CD workflow for a project. Covers job structure, caching, secrets handling, concurrency groups, environment gates, and reusable workflows via workflowcall. Invoked when the user asks to set up CI, add a GitHub Actions workflow, improve pipeline performance, or share workflow…
specflow
Spec-driven development with executable contracts.
specflow-loop-selector
Selects the correct Specflow loop and forces a concrete run contract before work starts. Use when an agent is asked to start Specflow work, build a ticket, create/refine a PRD, investigate an existing product, run Gate D, choose between spec-build and feature-build, or "go find out about" Specflow loops. Compatible…
specflow-simulate
Simulates end-to-end usage of a Specflow story across multiple personas and divergent routes to discover gaps, edge cases, and unhandled branches BEFORE the story is built — then proposes each finding as a concrete story addition (new REQ, negative-path AC, Gherkin branch, or journey step). This is the high-value…
specflow-audit
Audits a Specflow story/ticket for spec-compliance and surgically uplifts it — adding only the missing executable contract sections (SQL/RLS, TypeScript interfaces, invariant codes, Gherkin, acceptance criteria, Definition of Done, data-testid coverage) — then runs a pre-flight gate that refuses to mark the ticket…
architecture-review
Conducts a comprehensive multi-perspective architecture review using ALL architecture team members. Use when the user requests "Start architecture review", "Full architecture review", "Review architecture for version X.Y.Z", "Conduct comprehensive review", or when they want assessment from multiple perspectives. Do…