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/sitegit 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.00446 |
| Opus 5 | $0.00000 | $0.00223 |
| Sonnet 5 | $0.00000 | $0.00089 |
| Haiku 4.5 | $0.00000 | $0.00045 |
Grade A, and why
site 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
Site Management Commands
TL;DR (30 seconds)
- What: 15 commands for complete documentation site lifecycle (build, update, deploy, check)
- Why: Zero-to-deployed in minutes with smart automation
- How:
/folio:site:buildto compile,/folio:site:statusfor health check- Next: Run
/folio:site:updatefor content sync or/craft:site:deployto publish
Full documentation site lifecycle management - 15 commands.
When to Use What
| Scenario | Command | Why |
|---|---|---|
| Already have mkdocs.yml, need to build | /folio:site:build |
Compiles site without modifying config |
| Push to GitHub Pages | /craft:site:deploy |
Build + deploy in one step |
| Content changed, update site | /folio:site:update |
Sync code changes into site content |
| Check site health | /folio:site:check |
Validate config, links, deploy readiness |
Common confusion:
- build vs deploy —
buildcompiles locally;deploybuilds AND pushes to GitHub Pages - update vs build —
updatesyncs content from code changes;buildjust compiles existing content
Management Commands
/folio:site:status
Dashboard and health check
/folio:site:update
Update site content from code changes
/folio:site:build
Build site
/craft:site:deploy
Deploy to GitHub Pages
/folio:site:check
Validate site configuration, broken links, and deployment readiness
/folio:site:check # Full validation
/folio:site:check --links # Links only
Framework Support
/craft:site:docs/frameworks
Show supported documentation frameworks and their features
/craft:site:docs/frameworks
Supported:
- MkDocs Material (default)
- Docusaurus
- VuePress
- Sphinx
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 · 71 lines · 0 tokens per session scan A dc10d4c6506b
site 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 446 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.