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 commands/scolladon/craft/craft-rungit clone --depth 1 https://github.com/scolladon/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/commands/scolladon/craft/craft-run)<a href="https://agentmods.dev/commands/scolladon/craft/craft-run"><img src="https://agentmods.dev/badge/commands/scolladon/craft/craft-run.svg" alt="Measured on agentmods" 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 | $0.00026 | $0.00226 |
| Opus 5 | $0.00013 | $0.00113 |
| Sonnet 5 | $0.00005 | $0.00045 |
| Haiku 4.5 | $0.00003 | $0.00023 |
Grade A, and why
craft-run 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 4d 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.
What it actually says
craft-run
Input: $ARGUMENTS
Resolve the pipeline manifest first: run
node "${CRAFT_ROOT:-${CLAUDE_PLUGIN_ROOT}}/engine/bin/pipeline-resolve.js" "${CRAFT_ROOT:-${CLAUDE_PLUGIN_ROOT}}/pipeline/default.yml"
as a shell step before following the procedure below.
Follow skills/run/SKILL.md in this repository verbatim as the run procedure —
its preamble and numbered steps are the single source for flag parsing, manifest
and pipeline resolution, phase walking, and contract assembly; do not restate,
summarize, or re-derive them here. Thread $ARGUMENTS through exactly as that
skill's own $ARGUMENTS input, including any --profile, --skip, --config,
--harness, or --policy flags it may carry — the engine parses them identically
regardless of which binding dispatched this command.
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.
- 4d ago First seen · 20 lines · 26 tokens per session scan A 23c60b7cb550
craft-run is a command published in the GitHub repository scolladon/craft (2 stars, last pushed 16d ago), licensed MIT. It adds 26 tokens to every session and 226 once invoked, about $0.0001 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 commands, from other repositories
poc
Start a hypothesis-driven POC with hard timebox. Skips 80% of the production pipeline; forces ship/pivot/kill decision at expiry.
promote
Promote a POC to MVP/production. Runs the full audits that POC-mode skipped. Required before any POC can see production.
agent-retire
Gracefully retire an LLM agent from the workforce. Archives prompt, removes from sync list, keeps verdicts for audit. Like firing a human — but reversible.
prd
Create a Product Requirements Document — conversational intake, 8-section output. Run BEFORE architect to lock WHAT and WHY before the team decides HOW.
rfc
RFC process for cross-team decisions. Create, track, and close RFCs. Accepted RFCs auto-create ADRs.
spec
Spec Driven Development: interview → requirements.md + design.md + tasks.md. Run before writing any code.