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/scolladon/craft/implementationnpx skills add scolladon/craft --skill implementationgit clone --depth 1 https://github.com/scolladon/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.00035 | $0.00628 |
| Opus 5 | $0.00017 | $0.00314 |
| Sonnet 5 | $0.00007 | $0.00126 |
| Haiku 4.5 | $0.00003 | $0.00063 |
Grade A, and why
implementation 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 2d 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 — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
craft:implementation
Preamble (always runs — non-overridable)
- Manifest read (lint if standalone). Probe gates:
gates.part(else: repo test runner over touched files; else fall back togates.phaseper part — slower, never gateless) andgates.phase(else: repo validate/check/test script; if nothing exists, REFUSE to run this phase — a workflow without any gate is not this workflow). - The plan must exist and pass
plan-lint.sh(re-run it; cheap). - Memory read/write surface (advisory).
READS:
gate-cmdentry for this repo as an advisory hint — if a gate command was previously recorded, skip re-discovery but still run it (the gate is sacred; the hint only saves the probe, never the execution). A miss falls through to full gate probe as today. WRITES (buffered to run record, flushed at run end): the gate/test command discovered this run — stored as the BARE command only, with any leading env/secret assignment prefix stripped (neverTOKEN=… npm testor a command carrying a credential), since the store is committed; per-partsize+ pass/blockedoutcomefor each implemented part.
Procedure (default body — a manifest override: replaces everything below)
- Execute parts top-to-bottom, one craft:part-implementer per part,
sequential — never two agents writing one tree concurrently. Each spawn carries:
the working directory; the plan path (the agent reads the part there) + the part's
### Contextblock verbatim AND any load-bearing deltas — hand the pre-chew over so the agent never re-greps the codebase, but do NOT re-transcribe the whole committed part; the design doc path; the resolved part gate; the commit message from the plan; global + implementation-phasecontext:files verbatim. - After each agent returns, verify before launching the next: the commit exists
and matches the part promise (
git log,git show --stat); spot-check conventions on the diff. Failed/blocked part → fix in-session or escalate with the agent's options; dead agent → fresh respawn from the plan part (artifact handoff); never relaunch blindly. - Phase-boundary gate: after the LAST part, run
gates.phaseonce in-session. It MUST be green before the review phase — fix and commit anything it surfaces (fix(<scope>): close gate gap after part N).
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.
- 2d ago First seen · 44 lines · 35 tokens per session scan A 9dc6a1ef07eb
implementation is a skill published in the GitHub repository scolladon/craft (2 stars, last pushed 13d ago), licensed MIT. It adds 35 tokens to every session and 628 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
issue-triage
Issue triage: audit open issues, categorize, detect duplicates, cross-ref PRs, risk assessment, post comments. Args: "all" for deep analysis of all, issue numbers to focus (e.g. "42 57"), "en"/"fr" for language, no arg = audit only in French.
moai-ref-ui-polish
UI polish and interface-completion reference: the small visual details — concentric border radius, optical alignment, shadow-vs-border, motion easing, typography smoothing, tabular numbers, icon stroke weight, hit areas — that separate polished interfaces from generic ones. Agent-extending skill that amplifies…
kelos
Author, debug, and operate Kelos resources (Task, Session, Workspace, AgentConfig, TaskSpawner) on Kubernetes. Use for Kelos CRDs, resource manifests, the kelos CLI, or live cluster operations. Do not use for ordinary Kelos repo code edits, tests, reviews, build/CI, or git tasks unless they involve those resources.
trellis-brainstorm
Guides collaborative requirements discovery before implementation. Creates task directory, seeds PRD, asks high-value questions one at a time, researches technical choices, and converges on MVP scope. Use when requirements are unclear, there are multiple valid approaches, or the user describes a new feature or complex…
mulmoterminal-keys
Bind keyboard shortcuts and fix keyboard/clipboard behaviour in MulmoTerminal. Writes keymap, which Settings cannot set at all — its Keyboard shortcuts section is read-only, listing every action bound or not plus a send row. Explains copyOnSelect, questionPaneEnabled and terminalSubmit, which have their own Settings…
link-check
Verify @file references in AIWG skills and agents against the linking contract — per-file or corpus-wide, with optional auto-fix.