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-servicesnpx skills add bultcloud/mcp-server --skill bult-servicesgit 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.00024 | $0.00774 |
| Opus 5 | $0.00012 | $0.00387 |
| Sonnet 5 | $0.00005 | $0.00155 |
| Haiku 4.5 | $0.00002 | $0.00077 |
Grade A, and why
bult-services 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 — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Bult Services
Use When
Use this skill when the user asks to create, configure, update, start, stop, rebuild, delete, or inspect Bult services.
Required Context
Before creating or updating a service, collect:
- project ID or confirmed active project
- service name
- source type:
dockerorgit - Docker image, or Git repository URL and branch
- exposed ports
- service kind:
daemonordatabase - compute box ID if the default
1is not correct
Inspect Services
bult service list --json
bult status --json
Use service IDs for mutations when names are duplicated or unclear.
Create Docker Service
bult service create \
--name <name> \
--source-type docker \
--image <image> \
--port <port> \
--kind daemon
Multiple ports:
bult service create \
--name <name> \
--source-type docker \
--image <image> \
--port 80 \
--port 443
Create Git Service
bult service create \
--name <name> \
--source-type git \
--git-url <repository-url> \
--git-branch <branch> \
--port <port> \
--kind daemon
Create Flags
--name: required service name--source-type:dockerorgit, defaultdocker--image: Docker image for docker services--git-url: Git repository URL for git services--git-branch: Git branch, defaultmain--box-id: compute box ID, default1--kind:daemonordatabase, defaultdaemon--port: exposed port, repeatable
Verify creation:
bult service list --json
bult status --json
Update Service
service update reads JSON from stdin:
printf '%s\n' '<json-payload>' | bult service update <service-id>
Safe update workflow:
- Run
bult status --json. - Locate the exact service and preserve existing config not mentioned by the user.
- Build a valid JSON payload.
- Run
service updateagainst the service ID. - Verify with
bult status --json.
Do not remove envs, files, ports, or deploy fields unless the user explicitly asked for that removal.
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 · 141 lines · 24 tokens per session scan A 8b2230ffe6c6
bult-services is a skill published in the GitHub repository bultcloud/mcp-server (1 stars, last pushed 2mo ago), licensed MIT. It adds 24 tokens to every session and 774 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
deploy-docker-compose
Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack…
reproduce-issue
The single skill for reproducing an nx issue. Given a GitHub issue number (human entry) OR explicit repro parameters (agent entry), it runs the reproduction ENTIRELY inside an isolated Docker sandbox — gVisor on Linux, the Docker VM on macOS — so the untrusted repro's install scripts and commands never execute on the…
timoni
Use when deploying applications to Kubernetes with Timoni. Covers installing and upgrading module instances from OCI registries, composing multi-app deployments with bundles, injecting values from clusters or CI with runtimes, targeting multiple clusters, and authoring, testing, signing and publishing modules with CUE.
atmos-aws-ecr
AWS ECR commands in Atmos: atmos aws ecr login, ECR auth integrations, Docker credential writes, registry login via identity or explicit registry.
windows-builder
Build Windows images with Packer using WinRM communicator and PowerShell provisioners. Use when creating Windows AMIs, Azure images, or VMware templates.
release-openclaw-plugin-testing
Plan and run pre-release OpenClaw plugin validation across bundled plugins, package artifacts, lifecycle commands, doctor/fix, config round-trip, gateway startup, SDK compatibility, Docker E2E, Package Acceptance, and Testbox proof.