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/debugswift/xcodebazelmcp/cli-developmentnpx skills add DebugSwift/XcodeBazelMCP --skill cli-developmentgit clone --depth 1 https://github.com/DebugSwift/XcodeBazelMCPWhat 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.00034 | $0.00556 |
| Opus 5 | $0.00017 | $0.00278 |
| Sonnet 5 | $0.00007 | $0.00111 |
| Haiku 4.5 | $0.00003 | $0.00056 |
Grade A, and why
cli-development 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
CLI Development
Conventions
- Positional arg is the target/path/bundleId. Flags use
--kebab-case. - Repeatable flags (
--arg,--config,--launch-arg,--startup-arg) accumulate into arrays viaappend()helper. printToolis the universal CLI→MCP bridge: callscallBazelTool, prints text content, setsprocess.exitCodeon error.ToolContentis a union type ({ type: 'text'; text } | { type: 'resource'; ... }). UseextractText()helper to safely map to.text.
File Layout
| File | Responsibility |
|---|---|
src/cli.ts |
Thin dispatcher (~400 lines) |
src/cli/parsers.ts |
48 parse functions (~730 lines) |
src/cli/commands.ts |
runUpgrade, runDaemon, etc. (~240 lines) |
src/cli/help.ts |
printHelp (~160 lines) |
Streaming
--streamflag on build/test/clean/query usescallBazelToolStreamingwhich pipes chunks directly toprocess.stdout.write.- MCP streaming uses
notifications/progresswithprogressTokenfrom the client's_meta. - Structured output:
toolResult()returns bothcontent(human-readable) andstructuredContent(machine-parseable JSON withexitCode,command,output,target).
Log Streaming
log-startin CLI mode streams directly to stdout viaspawn('xcrun', [...], { stdio: ['ignore', 'inherit', 'inherit'] })— stops on Ctrl+C.- The MCP
log_capture_start/log_capture_stoppair uses in-memory capture (server stays alive between calls). sim-appearanceaccepts both--appearance darkflag anddarkas a positional arg.
Session Defaults
- Session defaults are in-memory per process — don't persist across CLI invocations (each
node dist/cli.jsis a new process). - In MCP server mode, they persist for the session.
- Profiles loaded from
config.yamlunderprofiles:key.activateProfilemerges profile defaults into session defaults. loadConfigFile()is lazy — called only once via aconfigLoadedguard.
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 · 45 lines · 34 tokens per session scan A 921b89e50888
cli-development is a skill published in the GitHub repository DebugSwift/XcodeBazelMCP (7 stars, last pushed 1mo ago), licensed MIT. It adds 34 tokens to every session and 556 once invoked, about $0.0002 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
test
Run tests. Use after code changes to validate. Arguments: unit (default, no GPU), e2e (with models), filter name, or all.
boutique-store
Create and use Boutique Store for Swift data persistence, including initialization, @Stored controllers, CRUD operations, operation chaining, and granular event monitoring. Use when persisting arrays of items, building data controllers, or working with Boutique's Store type.
boutique-stored-values
Persist individual values with Boutique's @StoredValue (UserDefaults) and @SecurelyStoredValue (Keychain), including set, reset, toggle, bindings, keypath setters, array and dictionary helpers, and async observation. Use when storing preferences, settings, feature flags, or sensitive data like auth tokens.
boutique-swiftui
Integrate Boutique with SwiftUI views using onChange, onStoreDidLoad, bindings, and preview stores. Use when building SwiftUI views that display or react to Boutique-persisted data.
analyze-db-logs
Analyze Drift / SQLite slow-query and super-slow-query logs against this app's known stall patterns (read waves, N+1, transaction scoping, MultiExecutor contention, WAL/OS factors).
review-comments
Fetch PR review comments, address each one in code, and post resolution replies.