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/data-wise/craft/gitgit 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.00000 | $0.00600 |
| Opus 5 | $0.00000 | $0.00300 |
| Sonnet 5 | $0.00000 | $0.00120 |
| Haiku 4.5 | $0.00000 | $0.00060 |
Grade A, and why
git 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.
How it starts
The opening of the file, as written. The whole thing — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git & CI Commands
Version control and continuous integration.
Note (2026-07 v4 consolidation): All git commands — worktree, sync, recap, init, branch protection, guard management, status, cleanup, and quick-branch creation — were folded into the
dev/gitskill; there are no longer separate slash commands under/craft:git:*. Ask naturally ("create a worktree for feature-auth", "protect this branch", "check guard status", "clean up merged branches") or seeskills/dev/git/SKILL.mddirectly.
Worktree vs Branch: When to Use What
| Scenario | Ask | Why |
|---|---|---|
| Start a new feature | "create a worktree for feature-x" | Isolated directory, no branch switching |
| Quick one-file fix | "create feature branch x" | Lightweight, stays in same directory |
| Work on 2+ features at once | "create a worktree for feature-x" | Each feature gets its own directory |
| Clean up after merge | "clean up merged branches" | Removes merged branches safely |
| See what's going on | "show git status" | Enhanced status with teaching mode support |
Decision rule: If the change takes more than one commit or you need to context-switch, use worktree. For quick fixes you'll commit immediately, use branch.
CI commands:
| Scenario | Command |
|---|---|
| What CI does my project need? | /craft:ci:detect |
| Generate GitHub Actions workflow | /craft:ci:generate |
| Validate existing CI config | /craft:ci:validate |
Git Commands (0)
Worktree, sync, recap, init, protect, unprotect, status, clean, branch, and
guard were all folded into the dev/git skill (2026-07 v4 consolidation) —
ask naturally ("create a worktree for feature-auth", "protect this branch",
"unprotect for a merge conflict", "check guard status", "clean up merged
branches", "create feature branch x") or see
skills/dev/git/SKILL.md.
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 · 70 lines · 0 tokens per session scan A a936af03832d
git is a command published in the GitHub repository Data-Wise/craft (4 stars, last pushed 16d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 600 tokens. 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
readme-audit
Audit a README's reading flow by treating it as a conversion funnel. Every section is evaluated against a target reader and a terminal action. Produces a structured audit blueprint that feeds directly into /readme-restructure.
readme-restructure
Execute a /readme-audit blueprint. Rewrites the README to the evaluator → conversion → links structure and creates linked docs by extracting and reorganising existing content.
build-fix
Fix build and type failures with minimal diffs.
checkpoint
Record a verified checkpoint before the next phase.
doctor
Check the install surface for missing files and invalid manifests.
feature-dev
Drive a feature from plan to implementation to review.