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/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/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="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.00055 | $0.00382 |
| Opus 5.5 | $0.00022 | $0.00153 |
| Sonnet 5.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 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
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.
- 1mo ago 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 (35 stars, last pushed 13d ago), licensed MIT. It adds 55 tokens to every session and 382 once invoked, about $0.0002 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-09-06.
Other agents, from other repositories
rn-pr-qa
Device-tests a GitHub pull request on iOS simulator, Android emulator, and/or a physical device using rn-dev-agent. Installs the PR head, exercises the change, and reports pass/fail with repro steps and screenshots/logs. PARENT-SESSION-ONLY: requires MCP tools (cdp, device, rnsession) — do NOT spawn via Task tool, run…
testing-specialist
Swift testing expert. Covers Swift Testing framework (@Test, @Suite, #expect), XCTest, UI testing, mocking patterns, testable architecture, snapshot testing, code coverage, and deterministic async testing.
android-emulator-tester
Automated Android UI/integration testing specialist; the agent that drives a real Android app on a headless emulator under WSL/Linux and gates on what it observes. Use when the task is "run the app on an emulator", "smoke-test a screen", "drive the Android UI", "reproduce a tap-and-crash / ANR", "automate an Android…
mobile-tester
Tests a Flutter or mobile app like a real user on an Android AVD or iOS simulator, verifying with parsed screenshots and integration tests. - Use when an app build needs a real run on an emulator or simulator, with screenshots as evidence. Read-only on source; reports pass/fail with evidence paths. Spawn one per app…
issue-worker
Lands one GitHub issue as its own pull request, or repairs one open pull request, alone in a worktree. Spawned by github-flow:dispatch and github-flow:shift.
mobile-mobile-qa
Mobile QA engineer that tests mobile applications, performs device testing, and ensures quality.