Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/bultcloud/mcp-servernpx agentmods add skills/bultcloud/mcp-server/bult-cli-operatorWrote 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/skills/bultcloud/mcp-server/bult-cli-operator)<a href="https://agentmods.dev/skills/bultcloud/mcp-server/bult-cli-operator"><img src="https://agentmods.dev/badge/skills/bultcloud/mcp-server/bult-cli-operator/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/bultcloud/mcp-server/bult-cli-operator"><img src="https://agentmods.dev/badge/skills/bultcloud/mcp-server/bult-cli-operator.svg" alt="Reviewed on agentmods" width="80" 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.00029 | $0.00908 |
| Opus 5.5 | $0.00012 | $0.00363 |
| Sonnet 5.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 1mo 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.
- 1mo 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 (2 stars, last pushed 7d ago), licensed MIT. It adds 29 tokens to every session and 908 once invoked, about $0.0001 per session on Opus 5.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
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
deck-retro
Run a fully local agent-deck retrospective over the user's own transcripts, Recall index and logs. Use when a user wants to find recurring failures or take their own finding from investigation through synthetic reproduction, a user-filed issue, a test-first fix and contributor PR handoff. Also use for weekly usage…
incident-response-incident-response
Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.
ci-fixer
CI failures - read error, minimal fix, verify.