A command for building and serving a project’s documentation website locally with Jekyll, a tool that generates websites from text files. It also runs the repository’s required supporting build steps.

Use it to install documentation dependencies, build the full docs site, and serve it at localhost:4000 for local inspection.

It provides the project’s prescribed documentation workflow and stops when a build step fails, making errors easier to identify.

build-docs — Command by untra

Install

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.

agentmods

npx agentmods add commands/untra/operator/build-docs

Clone the repo

git clone --depth 1 https://github.com/untra/operator

Made for: Claude Code.

Per session 11 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 362 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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	$0.00011	$0.00362
Opus 5	$0.00005	$0.00181
Sonnet 5	$0.00002	$0.00072
Haiku 4.5	$0.00001	$0.00036

Measured yesterday against content hash 8520b5304017, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

build-docs 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.

.claude/commands/build-docs.md · 26 lines

What it actually says

Build Docs

Build and serve the docs/ subproject locally for inspection. Stop immediately on any failure and report the error.

Workflow

Run each step sequentially from the repo root. If any step fails, stop and report the failure clearly.

Install Ruby dependencies: cd docs && bundle install
Build the full site: make docs from the repo root. This runs the whole pipeline in order — ts-rs bindings, the generated reference docs and hosted collection bundle (cargo run -- docs), the shared webcomponents/ bundle, the copy into docs/assets/js/, then Jekyll.
Serve locally: cd docs && bundle exec jekyll serve (run in background so the session remains interactive; serves on port 4000)
Report: Confirm the site is running at http://localhost:4000. Let the user know it auto-rebuilds on file changes.

Notes

Use make docs, not a bare bundle exec jekyll build. Jekyll alone will not regenerate the collection bundle or build the web components, so /workflows/ pages render an empty graph canvas.
bun is required for step 2 (the webcomponents/ build). docs/assets/js/ is a build artifact and is gitignored.
If port 4000 is already in use, report the conflict and suggest killing the existing process or using --port to pick a different one.
To stop the server later, kill the background Jekyll process.

Changes

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 · 26 lines · 11 tokens per session scan A 8520b5304017

Subscribe to this mod's changes

build-docs is a command published in the GitHub repository untra/operator (36 stars, last pushed 4d ago), licensed MIT. It adds 11 tokens to every session and 362 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-30.

Data and AI Git and workflow LLM Project management claude-code gemini-cli kanban tmux

build-docs

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

What it actually says

Build Docs

Workflow

Notes

What this file has done since we first saw it

Other commands, from other repositories

spec-kitty.analyze

flux-add

card

OPSX: Propose

wtfp:report-bug

aissue