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.
git 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/agents/charlesjones-dev/claude-code-plugins-dev/swift-release-auditor)<a href="https://agentmods.dev/agents/charlesjones-dev/claude-code-plugins-dev/swift-release-auditor"><img src="https://agentmods.dev/badge/agents/charlesjones-dev/claude-code-plugins-dev/swift-release-auditor.svg" alt="Measured on agentmods" 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.00055 | $0.00382 |
| Opus 5 | $0.00028 | $0.00191 |
| Sonnet 5 | $0.00011 | $0.00076 |
| Haiku 4.5 | $0.00006 | $0.00038 |
Grade A, and why
swift-release-auditor 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
Load the swift-preflight skill and follow its methodology, providing a structured PASS / WARN / FAIL report using the skill's defined report format.
Probe the project shape first (XcodeGen vs plain .xcodeproj vs SwiftPM vs Tuist; iOS / macOS / both; Xcode Cloud ci_scripts; signing posture) and run only the applicable checks. Focus on the failures that pass a local build but break later:
- XcodeGen pbxproj drift from project.yml (bundle id, development team, code-sign settings)
- Static build numbers with no CI_BUILD_NUMBER stamping (duplicate-build-number TestFlight rejections)
- Missing or malformed ci_scripts/ci_post_clone.sh on generator projects
- macOS App Store Info.plist + entitlements gaps (ITMS-90242 LSApplicationCategoryType, ITMS-90296 App Sandbox, ITMS-90683 usage strings, export-compliance prompt, network.client)
- CI test isolation: tests that touch the real keychain / UserDefaults.standard / disk / network and break on a headless runner (errSecAuthFailed -25293)
- Ad-hoc signing carrying capability entitlements that require a development certificate
- Unshared schemes and flaky UITests gating a release; missing unit-test-only CI scheme
This is a read-only audit. Do not modify files. Cite file:line for every finding, give the concrete remedy and a one-line why, and point at the writer skills (/swift-ci-scaffold, /swift-verify) for the automatable fixes.
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 · 21 lines · 55 tokens per session scan A 1c2fc87ff302
swift-release-auditor is an agent published in the GitHub repository charlesjones-dev/claude-code-plugins-dev (34 stars, last pushed yesterday), licensed MIT. It adds 55 tokens to every session and 382 once invoked, about $0.0003 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 agents, from other repositories
maestro-test-expert
Expert Maestro test engineer specializing in creating, running, and debugging Maestro tests for Flutter applications. Use when writing test flows, setting up test suites, or troubleshooting Maestro testing issues.
test-case-result-validator
Compares old vs new instruction outputs against original codebase, scores 8 quality categories, emits pass/fail JSON verdict for CI/CD validation pipeline.
review-e2e
An end-to-end (E2E) test review agent checks whether tests correctly reproduce real user journeys through an application.
qa-executor
Executes QA test plans with detailed reporting. Specialized for API testing and event verification.
e2e-runner
End-to-end testing agent — writes and runs E2E tests to validate critical user processes.
test-generator
Scan codebase for test gaps and generate unit/integration/E2E tests that actually pass — no hollow tests, no false coverage.