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 charlesjones-dev/claude-code-plugins-dev --skill swift-verifygit clone --depth 1 https://github.com/charlesjones-dev/claude-code-plugins-devWrote 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/charlesjones-dev/claude-code-plugins-dev/swift-verify)<a href="https://agentmods.dev/skills/charlesjones-dev/claude-code-plugins-dev/swift-verify"><img src="https://agentmods.dev/badge/skills/charlesjones-dev/claude-code-plugins-dev/swift-verify.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00086 | $0.01408 |
| Opus 5 | $0.00043 | $0.00704 |
| Sonnet 5 | $0.00017 | $0.00282 |
| Haiku 4.5 | $0.00009 | $0.00141 |
Grade A, and why
swift-verify 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.
How it starts
The opening of the file, as written. The whole thing — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Swift Verify
You run a Swift project's local quality gate, adapting the pipeline to how the project is built. This is the portable analog of a hand-written scripts/verify.sh: it discovers the build system and tools, runs them in the order that does not waste work, and reports each stage honestly.
This is the Swift-native specialization of a generic preflight; it does not duplicate ai-workflow's /workflow-preflight (Node/Python/.NET/Go/Rust). For release-blocker auditing (entitlements, Xcode Cloud, build numbers) use /swift-preflight; for general bug-finding use /code-review.
Arguments
$ARGUMENTS:
path- repo root (default cwd).--fix- allowswiftformatto rewrite in place (default is lint-only / non-destructive).--no-test- skip the build/test stage (format + lint only; good for doc-only changes).--destination=<dest>- override thexcodebuilddestination (e.g.platform=iOS Simulator,name=iPhone 16).
Phase 0: Detect build system + tools
- XcodeGen:
project.yml+command -v xcodegen. - Tuist:
Project.swift+command -v tuist. - Plain Xcode:
*.xcodeproj/*.xcworkspace, no generator. - SwiftPM:
Package.swift(library or executable).
Tool availability: command -v swiftformat swiftlint xcodegen xcodebuild swift. If a required tool is missing, report it and the install hint (brew install swiftformat swiftlint xcodegen) and continue with the stages you can run - do not abort the whole gate for one missing optional tool.
Config presence: .swiftformat, .swiftlint.yml. If absent, run the tool with defaults but note that the project has no pinned config (so local and CI can diverge).
Phase 1: Regenerate (generator projects only)
If XcodeGen: xcodegen generate (quiet). If Tuist: tuist generate.
Why first: newly added .swift files are not in the .xcodeproj until regen, and SourceKit diagnostics for them are stale. Regenerating makes xcodebuild authoritative. On a plain .xcodeproj or SwiftPM, skip this stage.
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 · 83 lines · 86 tokens per session scan A e32238f20440
swift-verify is a skill published in the GitHub repository charlesjones-dev/claude-code-plugins-dev (34 stars, last pushed yesterday), licensed MIT. It adds 86 tokens to every session and 1,408 once invoked, about $0.0004 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-09-06.
Other skills, from other repositories
axiom-swift-testing
Use when writing unit tests, adopting Swift Testing framework, making tests run faster without simulator, architecting code for testability, testing async code reliably, or migrating from XCTest - covers @Test/@Suite macros.
modernize-tests
Modernize test suites to use modern Swift Testing features or migrate from XCTest.
kotlin-testing
Kotlin testing patterns with Kotest, MockK, coroutine testing, property-based testing, and Kover coverage. Follows TDD methodology with idiomatic Kotlin practices. Use when writing Kotlin tests with Kotest or MockK, or testing coroutines and checking coverage.
kotlin-testing
Kotlin testing patterns with Kotest, MockK, coroutine testing, property-based testing, and Kover coverage. Follows TDD methodology with idiomatic Kotlin practices.
kotlin-testing
Kotlin testing patterns with Kotest, MockK, coroutine testing, property-based testing, and Kover coverage. Follows TDD methodology with idiomatic Kotlin practices.
swift-testing-expert
Expert guidance for Swift Testing: test structure, #expect/#require macros, traits and tags, parameterized tests, test plans, parallel execution, async waiting patterns, and XCTest migration. Use when writing new Swift tests, modernizing XCTest suites, debugging flaky tests, or improving test quality and…