Borrowing it
Nothing to install: this file belongs to Pratiyush/llm-wiki. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Pratiyush/llm-wiki/master/.claude/commands/wiki-build.mdgit clone --depth 1 https://github.com/Pratiyush/llm-wikiWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/commands/pratiyush/llm-wiki/wiki-build)<a href="https://agentmods.dev/commands/pratiyush/llm-wiki/wiki-build"><img src="https://agentmods.dev/badge/commands/pratiyush/llm-wiki/wiki-build.svg" alt="Measured on agentmods" height="20"></a>What 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.1 | $0.00000 | $0.00120 |
| Opus 5 | $0.00000 | $0.00060 |
| Sonnet 5 | $0.00000 | $0.00024 |
| Haiku 4.5 | $0.00000 | $0.00012 |
Grade A, and why
wiki-build 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 8d 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
Regenerate the static HTML site for the llmwiki.
Usage: /wiki-build [--synthesize]
Run:
python3 -m llmwiki build $ARGUMENTS
The --synthesize flag (optional) calls the claude CLI once to generate an Overview paragraph for the home page.
Report the output directory (default: site/), the total number of HTML files, and total size.
Remind the user they can browse the result with /wiki-serve (starts a local HTTP server on port 8765).
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.
- 8d ago First seen · 16 lines · 0 tokens per session scan A e793d2418585
wiki-build is a command published in the GitHub repository Pratiyush/llm-wiki (385 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 120 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-30.
Other commands, from other repositories
prompt-pilot
Rewrite a rough prompt into a precise, context-enriched prompt (read-only — never implements the task).
frontend-system-design
Produce a staff-grade frontend system-design RFC for the active task: a 12-section design document (problem, requirements, architecture, data model, API and interface contract, rendering and delivery, state management, performance budget, accessibility, security, rollout, trade-offs) covering web and mobile, persisted…
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.
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.