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 SteveGJones/ai-first-sdlc-practices --skill ios-signing-doctorgit clone --depth 1 https://github.com/SteveGJones/ai-first-sdlc-practicesWrote 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/stevegjones/ai-first-sdlc-practices/ios-signing-doctor)<a href="https://agentmods.dev/skills/stevegjones/ai-first-sdlc-practices/ios-signing-doctor"><img src="https://agentmods.dev/badge/skills/stevegjones/ai-first-sdlc-practices/ios-signing-doctor/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/stevegjones/ai-first-sdlc-practices/ios-signing-doctor"><img src="https://agentmods.dev/badge/skills/stevegjones/ai-first-sdlc-practices/ios-signing-doctor.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Rogue Agent · line 30 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
- medium Rogue Agent · line 46 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00065 | $0.01094 |
| Opus 5 | $0.00032 | $0.00547 |
| Sonnet 5 | $0.00013 | $0.00219 |
| Haiku 4.5 | $0.00006 | $0.00109 |
Grade A, and why
ios-signing-doctor 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 — 75 lines — stays where its author put it; the contents beside it link to each section on GitHub.
iOS Signing Doctor
Diagnose the code-signing / provisioning failure family — the single most common iOS release blocker —
and fix it, rather than guessing. Belongs to the ios-release-engineer discipline.
Arguments
error-message-or-log-path— paste the signing error or point at the build log (optional).
The mental model (why signing fails)
A build installs/runs only if four things agree: signing certificate (identity; private key in
Keychain, .p12 = cert+key) + App ID (bundle ID + capabilities) + provisioning profile (ties
cert + App ID + devices + entitlements, Apple-signed) + entitlements (must be a subset the App
ID/profile authorize). Most failures are a mismatch among these.
Steps
1. Inspect what is actually signed (don't guess)
security find-identity -v -p codesigning # usable signing identities
security cms -D -i embedded.mobileprovision # dump the profile plist
codesign -dv --entitlements :- MyApp.app # embedded entitlements (incl. get-task-allow, aps-environment)
codesign --verify --deep --strict MyApp.app # verify the signature
2. Match the symptom to the cause
| Symptom / error | Likely cause | Fix |
|---|---|---|
| "No signing certificate 'Apple Distribution' found" | Cert/private key not in keychain, or wrong team | Import the .p12; verify with security find-identity |
| "No profiles for 'com.acme.MyApp' were found" | No profile for that bundle ID + cert | Regenerate the profile (or fastlane match); check the exact bundle ID |
| "Provisioning profile doesn't include signing certificate" | Profile built against a different cert | Regenerate the profile with the current cert |
| "doesn't support the … capability" / "entitlements don't match" | Entitlement in the binary not enabled on the App ID / not in the profile | Enable the capability on the App ID, regenerate the profile — or remove the stray entitlement you don't actually use |
| "Provisioning profile has expired" | Dev/Ad Hoc profile past expiry | Regenerate |
errSecInternalComponent on CI codesign |
Keychain locked / partition list not set | security set-key-partition-list -S apple-tool:,apple: -s -k <pw> <keychain> |
| Upload rejected: "Invalid Provisioning Profile … get-task-allow" | Debug entitlement in a store build | Archive with Release config + distribution profile (see below) |
| Bundle ID mismatch | Info.plist CFBundleIdentifier ≠ App ID |
Align exactly (case-sensitive) |
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 · 75 lines · 65 tokens per session scan A 216016c7f6a6
ios-signing-doctor is a skill published in the GitHub repository SteveGJones/ai-first-sdlc-practices (41 stars, last pushed 1mo ago), licensed MIT. It adds 65 tokens to every session and 1,094 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-03.
Other skills, from other repositories
ios-fix
Autonomous iOS bug fixer. (gstack).
google-mobile-ads-validate
Validates a project's Google Mobile Ads (GMA) SDK integration for iOS, Android, or Unity projects. Use when conducting a full pre-launch audit of an app that integrates GMA SDK or when validating any individual GMA SDK integration checks, such as when validating ad unit IDs and ad formats, SKAdNetwork IDs, mediation…
competition-ios-runtime
Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for IPA runtime analysis, Frida hooks, Objective-C or Swift method tracing, Keychain inspection, SSL pinning bypass, URL scheme handling, and iOS request-signing recovery. Use when the user asks to hook an IPA, trace Objective-C or Swift…
swiftui-performance-audit
SwiftUI performance: render, scroll, CPU/memory, updates, layout, Instruments.
android-tombstone-symbolication
Symbolicate the .NET runtime frames in an Android tombstone file. Extracts BuildIds and PC offsets from the native backtrace, downloads debug symbols from the Microsoft symbol server, and runs llvm-symbolizer to produce function names with source file and line numbers. USE FOR triaging a .NET MAUI or Mono Android app…
node-connect
Diagnose OpenClaw node connection and pairing failures for Android, iOS, and macOS companion apps. Use when QR/setup code/manual connect fails, local Wi-Fi works but VPS/tailnet does not, or errors mention pairing required, unauthorized, bootstrap token invalid or expired, gateway.bind, gateway.remote.url, Tailscale…