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/claude-plugins/sitegit clone --depth 1 https://github.com/Data-Wise/claude-pluginsWhat 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.00667 |
| Opus 5 | $0.00000 | $0.00333 |
| Sonnet 5 | $0.00000 | $0.00133 |
| Haiku 4.5 | $0.00000 | $0.00067 |
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.
How it starts
The opening of the file, as written. The whole thing — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Site Management Commands
TL;DR (30 seconds)
- What: 15 commands for complete documentation site lifecycle (create, update, deploy, theme)
- Why: Zero-to-deployed in minutes with 8 ADHD-friendly presets and smart automation
- How:
/craft:site:create --preset adhd-focusfor instant site,/craft:site:statusfor health check- Next: Explore the 8 design presets below or run
/craft:site:updatefor content sync
Full documentation site wizard with 8 ADHD-friendly design presets - 15 commands.
/craft:site:create
Purpose: Zero to deployed documentation site in minutes.
Features:
- 8 ADHD-friendly design presets
- Auto project detection
- Smart navigation structure
- GitHub Pages deployment setup
Usage:
/craft:site:create # Interactive wizard
/craft:site:create --preset data-wise # Use preset directly
/craft:site:create --quick # Minimal prompts (auto-detect)
Presets:
data-wise- DT's standard (blue/orange)minimal- Clean and simpleopen-source- Community-friendlycorporate- Professionaladhd-focus- Calm forest greenadhd-calm- Warm earth tonesadhd-dark- Dark-firstadhd-light- Warm light
Navigation & Audit Commands
/craft:site:nav
Navigation reorganization (ADHD-friendly, max 7 sections)
/craft:site:nav
/craft:site:audit
Content inventory & audit (outdated, duplicates, gaps)
/craft:site:audit
/craft:site:consolidate
Merge duplicate/overlapping documentation files
/craft:site:consolidate
Management Commands
/craft:site:status
Dashboard and health check
/craft:site:update
Update site content from code changes
/craft:site:theme
Quick theme changes (colors, presets, fonts)
/craft:site:build
Build site
/craft:site:preview
Preview locally
/craft:site:deploy
Deploy to GitHub Pages
/craft:site:init
Basic initialization (use create for full wizard)
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 · 126 lines · 0 tokens per session scan A a9e99ac56fbd
site is a command published in the GitHub repository Data-Wise/claude-plugins (7 stars, last pushed 5d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 667 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
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.