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 SethCalkins/claude-ios-swift-plugin --skill gh-issue-fix-flowgit 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/skills/sethcalkins/claude-ios-swift-plugin/gh-issue-fix-flow)<a href="https://agentmods.dev/skills/sethcalkins/claude-ios-swift-plugin/gh-issue-fix-flow"><img src="https://agentmods.dev/badge/skills/sethcalkins/claude-ios-swift-plugin/gh-issue-fix-flow/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/skills/sethcalkins/claude-ios-swift-plugin/gh-issue-fix-flow"><img src="https://agentmods.dev/badge/skills/sethcalkins/claude-ios-swift-plugin/gh-issue-fix-flow.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.00066 | $0.00516 |
| Opus 5 | $0.00033 | $0.00258 |
| Sonnet 5 | $0.00013 | $0.00103 |
| Haiku 4.5 | $0.00007 | $0.00052 |
Grade A, and why
gh-issue-fix-flow 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 12d 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.
This is a copy
100% identical to gh-issue-fix-flow — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Gh Issue Fix Flow
Overview
Resolve a GitHub issue from intake through fix, validation, and push using gh, local edits, XcodeBuildMCP, and git.
Workflow
1) Intake and issue context
- Use
gh issue view <id> --repo <owner/repo> --commentsto get the full issue context. - If the repo is unclear, run
gh repo view --json nameWithOwnerto confirm. - Capture reproduction steps, expected behavior, and any maintainer notes.
2) Locate the code path
- Use
rg -nto locate likely files and entry points. - Read the relevant code paths with
sed -norrg -ncontext. - Follow repo-specific conventions (AGENTS/CLAUDE instructions).
3) Implement the fix
- Edit the minimal set of files.
- Keep changes aligned with existing architecture and style.
- Add tests when behavior changes and test coverage is practical.
4) Build and test
- Use XcodeBuildMCP for required builds/tests:
- Set defaults once:
mcp__XcodeBuildMCP__session-set-defaults. - Build:
mcp__XcodeBuildMCP__build_macosormcp__XcodeBuildMCP__build_sim. - Tests: prefer targeted schemes (e.g.,
mcp__XcodeBuildMCP__test_sim).
- Set defaults once:
- If macOS tests fail due to deployment target mismatches, run the equivalent iOS simulator tests.
- Report warnings or failures; do not hide them.
5) Commit and push
- Check for unrelated changes with
git status --short. - Stage only the fix (exclude unrelated files).
- Commit with a closing message:
Fix … (closes #<issue>). - Push with
git push.
6) Report back
- Summarize what changed and where.
- Provide test results (including failures).
- Note any follow-ups or blocked items.
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.
- 12d ago First seen · 53 lines · 66 tokens per session scan A 69c36d7ce1db
gh-issue-fix-flow is a skill published in the GitHub repository SethCalkins/claude-ios-swift-plugin (2 stars, last pushed 7mo ago), licensed MIT. It adds 66 tokens to every session and 516 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to gh-issue-fix-flow, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
agent-merge-conflict-arbiter
Neutral arbiter for merge conflicts between two agents.
git-advanced-workflows
Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.
bisect
Bisect regressions or broken builds in the Chromium repository using deterministic binary search, checking out midpoint commits, syncing dependencies with gclient sync, compiling the target with autoninja, and querying the user for test results until the culprit commit is isolated.
mantis-critic
Assesses the production viability of findings, filtering out debug-only features and assertion traps. Use when findings have been validated and you need to confirm they are triggerable in production release builds (with assertions disabled). Don't use for writing reproduction scripts or patches.
hotpath_bump
Bump the hotpath version number across the workspace and related files. Updates crate versions in Cargo.toml files (exact patch version) and version references in the backend middleware, hotpathinit skill, and README (major.minor only). Use when the user wants to bump, bump the version, or release a new hotpath…
cy-orquestrate-issue
Orchestrate GitHub bug resolution through a new CompozyOS managed worktree and Codex Astra High session per issue. Investigate reported bugs, create missing issues, and dispatch a Goal-backed executor responsible for a detailed PR, green CI, and all CodeRabbit and Greptile feedback. Use when asked to delegate issue…