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 skills/bultcloud/mcp-server/bult-cli-operatornpx skills add bultcloud/mcp-server --skill bult-cli-operatorgit clone --depth 1 https://github.com/bultcloud/mcp-serverWhat 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.00029 | $0.00908 |
| Opus 5 | $0.00015 | $0.00454 |
| Sonnet 5 | $0.00006 | $0.00182 |
| Haiku 4.5 | $0.00003 | $0.00091 |
Grade A, and why
bult-cli-operator 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.
How it starts
The opening of the file, as written. The whole thing — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Bult CLI Operator
Use When
Use this skill when the user asks an AI agent to manage Bult from a terminal: authenticate, inspect account/project state, choose a project, manage services, deploy, read logs, or debug runtime state.
Agent Contract
You are operating infrastructure for the user. Prefer explicit, reversible, auditable CLI actions. Do not guess project IDs, service IDs, API tokens, Docker images, repository URLs, exposed ports, or destructive intent.
Prerequisites
Check that the CLI is available:
bult --help
If working inside the Bult CLI source checkout and no installed binary exists, use:
go run ./cmd/bult --help
In later examples, replace bult with go run ./cmd/bult only for source-checkout operation.
Shell Completion
Use completion commands when the user asks to set up tab completion:
bult completion bash
bult completion zsh
bult completion fish
bult completion powershell
Ask before writing to shell startup files, Homebrew completion directories, /etc, or PowerShell profiles. For a temporary current-session setup, follow the shell-specific instructions from:
bult completion <shell> --help
Authentication
Check authentication with a read-only command:
bult project list --json
If the CLI reports that the user is not logged in, ask the user to run:
bult login
bult login prompts for an API token. Never print, log, summarize, or ask the user to paste their token into normal chat unless they explicitly choose to.
Optional custom API URL:
bult login --api-url <api-url>
Logout:
bult logout
Project Resolution
Bult resolves the active project in this order:
--project <project-id>.bult.yamlin the current directory- the default project stored in
~/.bult/config.json
For automation, prefer passing --project <project-id> unless the user wants the current directory linked.
Read the active project:
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 · 160 lines · 29 tokens per session scan A 70f73e1031f7
bult-cli-operator is a skill published in the GitHub repository bultcloud/mcp-server (1 stars, last pushed 2mo ago), licensed MIT. It adds 29 tokens to every session and 908 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…