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/teamniteo/hakuto/initgit clone --depth 1 https://github.com/teamniteo/hakutoWhat 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.00011 | $0.00650 |
| Opus 5 | $0.00005 | $0.00325 |
| Sonnet 5 | $0.00002 | $0.00130 |
| Haiku 4.5 | $0.00001 | $0.00065 |
Grade A, and why
init 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.
What it actually says
Scaffold a new Hakuto site in the current working directory.
Run this one Bash block — it guards, scaffolds, and inits git atomically. If the guard trips, the copy never happens.
set -e
# Guard: refuse if target already has an Astro/Hakuto project
for f in package.json src CLAUDE.md astro.config.mjs astro.config.ts; do
if [ -e "$f" ]; then
echo "ERROR: $f already exists. /hakuto:init needs a clean directory." >&2
exit 1
fi
done
# Copy full scaffold (incl. dotfiles and .claude/)
cp -a "${CLAUDE_PLUGIN_ROOT}/scaffold/." ./
# Sanity check the copy
ls package.json astro.config.mjs CLAUDE.md >/dev/null
# Initialize git (scaffold ships a .gitignore)
[ -d .git ] || git init -q -b main
# Record scaffold baseline for future `scaffold-sync` runs (best-effort; skill auto-baselines if missing).
if SCAFFOLD_SHA=$(git -C "${CLAUDE_PLUGIN_ROOT}" rev-parse HEAD 2>/dev/null); then
PLUGIN_VERSION=$(jq -r '.version // "unknown"' "${CLAUDE_PLUGIN_ROOT}/.claude-plugin/plugin.json" 2>/dev/null || echo "unknown")
printf '{"last_synced_sha":"%s","last_synced_at":"%s","last_sync_method":"git","last_synced_plugin_version":"%s","schema_version":1}\n' \
"$SCAFFOLD_SHA" "$(date -u +%Y-%m-%dT%H:%M:%SZ)" "$PLUGIN_VERSION" > .hakuto-sync.json
fi
echo "Scaffold complete."
If the guard trips, stop. Tell the user to run /hakuto:init in a clean directory (or remove the conflicting files first). Do not proceed to any other step.
After a successful scaffold, output this verbatim
Hakuto scaffold ready. Next:
bun install(ordevenv upif you use devenv — bun is already declared)bun run dev— opens http://localhost:4321git add -A && git commit -m "Initial scaffold"— a local git repo was initialized for you- Describe your site ("Build me a landing page for a coffee roaster") and the
website-builderskill will take over.Skills and agents come from the installed plugin and update via
/plugin update hakuto.Not using devenv? Delete
devenv.nix,devenv.yaml, and.envrc. Nothing else depends on them.
Do not run bun install, bun run dev, or any git commands yourself — the user runs those.
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 · 56 lines · 11 tokens per session scan A 7a3449d21b1f
init is a command published in the GitHub repository teamniteo/hakuto (5 stars, last pushed 7d ago), licensed MIT. It adds 11 tokens to every session and 650 once invoked, about $0.0001 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
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.