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/SethCalkins/claude-ios-swift-pluginWrote 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/commands/sethcalkins/claude-ios-swift-plugin/swift-fix-issue)<a href="https://agentmods.dev/commands/sethcalkins/claude-ios-swift-plugin/swift-fix-issue"><img src="https://agentmods.dev/badge/commands/sethcalkins/claude-ios-swift-plugin/swift-fix-issue/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/commands/sethcalkins/claude-ios-swift-plugin/swift-fix-issue"><img src="https://agentmods.dev/badge/commands/sethcalkins/claude-ios-swift-plugin/swift-fix-issue.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.00018 | $0.00741 |
| Opus 5 | $0.00009 | $0.00370 |
| Sonnet 5 | $0.00004 | $0.00148 |
| Haiku 4.5 | $0.00002 | $0.00074 |
Grade A, and why
swift-fix-issue 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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fix GitHub Issue
End-to-end workflow to fix a GitHub issue: intake, implement, test, commit, and push.
Instructions
1. Intake and issue context
-
Get issue details:
gh issue view <issue-number> --comments- If repo unclear, run
gh repo view --json nameWithOwner
- If repo unclear, run
-
Extract key information:
- Problem description
- Reproduction steps
- Expected vs actual behavior
- Any maintainer notes or labels
-
Summarize understanding to user before proceeding
2. Locate the code path
- Use Grep to find relevant files and entry points
- Read the affected code paths
- Follow repo conventions (check CLAUDE.md, AGENTS.md)
- Identify the minimal set of files to change
3. Implement the fix
- Edit minimal files - avoid scope creep
- Follow existing patterns - match architecture and style
- Add tests if behavior changes and coverage is practical
- Document any non-obvious changes with comments
4. Build and test
-
Set XcodeBuildMCP defaults:
mcp__XcodeBuildMCP__session-set-defaults -
Build:
- iOS:
mcp__XcodeBuildMCP__build_sim - macOS:
mcp__XcodeBuildMCP__build_macos
- iOS:
-
Run tests:
- Prefer targeted test schemes
- Run
mcp__XcodeBuildMCP__test_simortest_macos
-
Report all results - don't hide warnings or failures
5. Commit and push
-
Check status:
git status --short -
Stage only the fix - exclude unrelated changes
-
Commit with closing message:
git commit -m "Fix [description] (closes #<issue-number>)" -
Push:
git push
6. Report back
Provide summary:
- What changed and where
- Test results (including any failures)
- Follow-ups or blocked items
- Link to the commit
Output Format
## Issue #123 Fixed
### Summary
Fixed the crash when loading user profile with missing avatar URL.
### Changes
- `UserProfile.swift:42` - Added nil check for avatar URL
- `UserProfileTests.swift` - Added test for missing avatar case
### Test Results
- Build: SUCCESS
- Tests: 23 passed, 0 failed
### Commit
`abc1234` - Fix crash on missing avatar URL (closes #123)
### Notes
- Consider adding server-side validation for avatar URLs (follow-up)
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.
- 9d ago First seen · 123 lines · 18 tokens per session scan A ac6e615bcca7
swift-fix-issue is a command published in the GitHub repository SethCalkins/claude-ios-swift-plugin (2 stars, last pushed 7mo ago), licensed MIT. It adds 18 tokens to every session and 741 once invoked, about $0.0001 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.