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/restoregit 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.00008 | $0.00670 |
| Opus 5 | $0.00004 | $0.00335 |
| Sonnet 5 | $0.00002 | $0.00134 |
| Haiku 4.5 | $0.00001 | $0.00067 |
Grade A, and why
restore 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/restore - Restore Git & Session Context
This command is a thin shim. The canonical behavior lives in two skills: git-activity recap (
dev/gitskill, Operation 7) and.STATUS-based session recap (adhd-workflowskill, §2 "Context Restoration"). This file exists to give both a single, discoverable combined entry point — seedocs/specs/SPEC-craft-restore-2026-07-17.md.
Usage
/craft:restore # default mode
/craft:restore detailed # full verbosity on the git-activity portion
/craft:restore summary # minimal verbosity on the git-activity portion
When invoked
- Session state: run the
adhd-workflowskill's §2 "Context Restoration (recap)" operation —.STATUSstate, git activity (last 48h), open PRs/issues, planning files, Obsidian flow status. This is single-verbosity; the mode argument does not change it. - Git activity: run the
dev/gitskill's Operation 7 (git activity recap) — today's/this week's commits, branch ahead/behind, unpushed work, open PRs — using whichever mode (default|detailed|summary) was passed. - De-dupe on presentation, not on source logic: both operations independently
surface recent commits and open PRs. Present one combined git-activity block
(from step 2, mode-aware) rather than printing the same commits/PRs twice.
Session-only content from step 1 (
.STATUSnext-action/blockers, planning files, Obsidian flow status) goes in its own section. - Present as one combined, ADHD-friendly summary: git state first, session state second, a single "what's next" line last.
- Do not reimplement either operation here. Any change to git-recap logic
belongs in
dev/git; any change to session-recap logic belongs inadhd-workflow. This file is routing only.
Read-only
/craft:restore never writes .STATUS, never commits, never syncs anything — it
only reads and reports. There is no --sync flag (unlike savant:restore, which
optionally applies diff-gated doc updates). If write-back is ever wanted, that is
a separate, explicitly-scoped addition — not part of this command today.
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 · 54 lines · 8 tokens per session scan A a1eb807984e7
restore is a command published in the GitHub repository Data-Wise/craft (4 stars, last pushed 16d ago), licensed MIT. It adds 8 tokens to every session and 670 once invoked, about $0.0000 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
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.