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 skills add bultcloud/mcp-server --skill bult-projectsgit clone --depth 1 https://github.com/bultcloud/mcp-serverWrote 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-projects)<a href="https://agentmods.dev/skills/bultcloud/mcp-server/bult-projects"><img src="https://agentmods.dev/badge/skills/bultcloud/mcp-server/bult-projects/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-projects"><img src="https://agentmods.dev/badge/skills/bultcloud/mcp-server/bult-projects.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.00021 | $0.00422 |
| Opus 5.5 | $0.00008 | $0.00169 |
| Sonnet 5.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 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.
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.
- 1mo ago First seen · 105 lines · 21 tokens per session scan A ae9cdb82d160
bult-projects is a skill published in the GitHub repository bultcloud/mcp-server (2 stars, last pushed 7d ago), licensed MIT. It adds 21 tokens to every session and 422 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
story-readiness
Is a story implementation-ready? Checks clear acceptance criteria, open questions, ADR refs. READY/NEEDS WORK/BLOCKED/NOT ASSESSED.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…