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-projectsnpx skills add bultcloud/mcp-server --skill bult-projectsgit 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.00021 | $0.00422 |
| Opus 5 | $0.00010 | $0.00211 |
| Sonnet 5 | $0.00004 | $0.00084 |
| Haiku 4.5 | $0.00002 | $0.00042 |
Grade A, and why
bult-projects 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.
What it actually says
Skill: Bult Projects
Use When
Use this skill when the user asks to create, list, select, link, inspect, or delete Bult projects.
Required Context
Before changing projects, identify:
- desired project name or project ID
- whether the current directory should be linked to the project
- whether deletion is explicitly intended
List Projects
bult project list --json
Summarize project names, IDs, service counts, and creation dates.
Create A Project
bult project create <name>
After creation, verify it appears:
bult project list --json
If the user wants to work in it immediately, either pass --project <project-id> in future commands or link the directory:
bult link <project-id>
Link Current Directory
Run this from the user's target application directory, not from an arbitrary shell location:
bult link <project-id>
This writes .bult.yaml:
project_id: <project-id>
Verify:
bult status --json
Do not overwrite an existing .bult.yaml unless the user wants this directory relinked.
Select Default Project
Interactive:
bult project select
Use only when the agent can interact with a terminal picker or when the user is driving the terminal.
For non-interactive workflows, use:
bult --project <project-id> status --json
Delete A Project
Deletion is destructive. Confirm the exact project name and ID first:
bult project list --json
Then run only after explicit user intent:
bult project delete <project-id> --force
Verify:
bult project list --json
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 · 105 lines · 21 tokens per session scan A ae9cdb82d160
bult-projects is a skill published in the GitHub repository bultcloud/mcp-server (1 stars, last pushed 2mo ago), licensed MIT. It adds 21 tokens to every session and 422 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.
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…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
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.