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 OutlineDriven/odin-claude-plugin --skill ios-build-fixgit clone --depth 1 https://github.com/OutlineDriven/odin-claude-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/outlinedriven/odin-claude-plugin/ios-build-fix)<a href="https://agentmods.dev/skills/outlinedriven/odin-claude-plugin/ios-build-fix"><img src="https://agentmods.dev/badge/skills/outlinedriven/odin-claude-plugin/ios-build-fix/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/outlinedriven/odin-claude-plugin/ios-build-fix"><img src="https://agentmods.dev/badge/skills/outlinedriven/odin-claude-plugin/ios-build-fix.svg" alt="Reviewed on agentmods" width="80" 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.00049 | $0.02398 |
| Opus 5 | $0.00024 | $0.01199 |
| Sonnet 5 | $0.00010 | $0.00480 |
| Haiku 4.5 | $0.00005 | $0.00240 |
Grade A, and why
ios-build-fix 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 3d 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
iOS build fix
Mode A — Debug-bridge UI-fix
Contract
| Field | Bound contract |
|---|---|
| Trigger | the user runs /ios-build-fix |
| Authority | Reversible local: writes the iOS project's Swift source plus snapshot and screenshot fixtures and the regression test under test/fixtures/ios-fix/, applied and verified through the iOS debug bridge; rollback is version control. No remote mutation. The user picks among competing root-cause fixes. |
| Side effect | project code changes edited directly, rebuilt and verified through the debug bridge, plus snapshot and screenshot fixtures and a regression test written under test/fixtures/ios-fix/ |
| Done | the failing iOS behavior is fixed and verified on a device or simulator, with a reproducing snapshot and a regression test committed alongside the fix |
Inputs
Required:
- A bug finding with a description of the failing behavior, a screenshot, and the suspected accessibility-tree node. Supplied by the user or a prior QA pass.
- The iOS debug bridge (StateServer) running with a connected device or simulator, identified by UDID.
- The Xcode scheme name and build destination.
Optional:
- The user's choice among plausible root causes, if more than one remains after source tracing.
Procedure
- Do not edit any Swift source until a
GET /state/snapshotthat reproduces the bug is captured. A fix without a reproducing snapshot is rejected. - Read the bug finding (description, screenshot, suspected accessibility-tree node).
- Drive the device into the bug state through the debug bridge:
POST /tap,POST /swipe,POST /type, orPOST /state/<key>(snapshot-eligible fields only). - Capture
GET /state/snapshotand write it totest/fixtures/ios-fix/<bug-slug>-pre.json. - Capture
GET /screenshotand write it totest/fixtures/ios-fix/<bug-slug>-pre.png. - Record one line stating what is wrong and the expected behavior.
- Locate the root cause. Read the Swift source and trace the buggy screen back to the view model, data flow, and state mutation. Identify the smallest change that fixes the behavior.
- If more than one plausible root cause remains, present them to the user and let the user pick the one to fix before editing.
- Apply the fix: edit the Swift source, keeping the diff minimal. Rollback path:
git checkout -- <edited files>reverts this edit. - Rebuild and reinstall:
xcodebuild -scheme <SchemeName> -destination <BuildDestination> build, thenxcrun simctl install <UDID> <app-path>on a simulator orios-deploy --bundle <app-path> --id <UDID>on a device. The daemon reconnects the StateServer tunnel after the rebuild; re-deploy through the boot-token rotation flow. - Verify:
POST /state/restorewith the pre-bug snapshot to reproduce the state, then take a freshGET /screenshotand compare it againsttest/fixtures/ios-fix/<bug-slug>-pre.png. - If the bug visibly persists, the fix did not work: revert the Swift edit (
git checkout -- <edited files>) and retry from step 9, up to 3 iterations before escalating to the user. - If the bug is gone, capture
test/fixtures/ios-fix/<bug-slug>-post.png. - Add a regression test at
test/fixtures/ios-fix/<bug-slug>.test.tsthat loads the pre-bug snapshot, restores it viaPOST /state/restore, and asserts the post-fix behavior on a real device (gated on a device-available flag). - Commit the snapshot fixture, the pre-fix and post-fix screenshots, and the regression test alongside the Swift fix.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago Changed · +46 lines · +7 tokens per session b10f4ab6f76b
- 5d ago First seen · 55 lines · 42 tokens per session scan A bf2b674c5e96
ios-build-fix is a skill published in the GitHub repository OutlineDriven/odin-claude-plugin (35 stars, last pushed 2d ago), licensed Apache-2.0. It adds 49 tokens to every session and 2,398 once invoked, about $0.0002 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-04.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…