swift-build

swift-build is a command for Claude Code from jeremieb/swift-unit-test-instructions. It costs 0 tokens per session (352 once invoked), scanned A, original, MIT.

A build-check command for Swift projects. It detects whether the project uses an Xcode workspace, Xcode project, or Swift Package, then runs the appropriate build.

In plain words
What is it for?
Use it after Swift changes to find build errors and warnings, select an Xcode scheme, and report whether the build succeeded or failed.
Why use it?
It provides a repeatable check that code changes still compile before the work is considered complete.

Command for Claude Code

Written for Claude Code: installed under .claude/.

Good fit Use it after Swift changes to find build errors and warnings, select an Xcode scheme, and report whether the build succeeded or failed.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/jeremieb/swift-unit-test-instructions/swift-build
Install

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.

Clone the repo
git clone --depth 1 https://github.com/jeremieb/swift-unit-test-instructions

Made for: Claude Code.

Wrote 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.

agentmods badge for swift-build

README.md
[![agentmods](https://agentmods.dev/badge/commands/jeremieb/swift-unit-test-instructions/swift-build/github.svg)](https://agentmods.dev/commands/jeremieb/swift-unit-test-instructions/swift-build)
Your own site
<a href="https://agentmods.dev/commands/jeremieb/swift-unit-test-instructions/swift-build"><img src="https://agentmods.dev/badge/commands/jeremieb/swift-unit-test-instructions/swift-build/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.

agentmods 80×15 button for swift-build

Your own site · 80×15
<a href="https://agentmods.dev/commands/jeremieb/swift-unit-test-instructions/swift-build"><img src="https://agentmods.dev/badge/commands/jeremieb/swift-unit-test-instructions/swift-build.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 352 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00000 $0.00352
Opus 5 $0.00000 $0.00176
Sonnet 5 $0.00000 $0.00070
Haiku 4.5 $0.00000 $0.00035

Measured 8d ago against content hash 279298c2a0e3, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

swift-build 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 8d 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.

.claude/commands/swift-build.md · 61 lines

What it actually says

Validate that the Swift project builds successfully. Run this after any code change before considering work done.

Steps

1. Detect project type

Look for (in order):

  • *.xcworkspace → use xcodebuild with workspace
  • *.xcodeproj → use xcodebuild with project
  • Package.swift → use swift build

2. Find scheme

For xcodebuild projects, read available schemes:

xcodebuild -list 2>/dev/null

Use the first non-test scheme found. If ambiguous, ask the user which scheme to use.

3. Run the build

Xcode project / workspace:

xcodebuild build \
  -scheme "$SCHEME" \
  -destination "generic/platform=iOS Simulator" \
  -quiet 2>&1 | grep -E "error:|warning:|BUILD SUCCEEDED|BUILD FAILED"

Swift Package:

swift build 2>&1

4. Report result

On success:

BUILD SUCCEEDED
Scheme: $SCHEME
No errors or warnings.

On failure:

BUILD FAILED
Scheme: $SCHEME

Errors:
- $FILE:$LINE — $ERROR_MESSAGE

5. On failure — attempt fix (max 2 attempts)

  • Read each file containing an error
  • Apply the fix
  • Re-run the build
  • If still failing after 2 attempts: stop, present the remaining errors, and ask the user how to proceed

Never force-ignore compiler errors with @discardableResult, forced casts, or suppression comments.

Changes

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.

  1. 8d ago First seen · 61 lines · 0 tokens per session scan A 279298c2a0e3

Subscribe to this mod's changes

swift-build is a command published in the GitHub repository jeremieb/swift-unit-test-instructions (5 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 352 tokens. 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.