Competition iOS Runtime is a downstream skill of the CTF Sandbox Orchestrator. It applies when the decisive path in a challenge runs through live iOS trust boundaries such as request signers, certificate checks and Keychain reads.
The agent starts with static triage of the bundle, then hooks the narrowest runtime boundary that changes server acceptance, and finally rebuilds the smallest stateful request that the server accepts. The original IPA, the extracted bundle and any decrypted or re-signed copy are kept as separate artifacts.
What You Get
- A quick start that preserves each version of the app as its own artifact
- A static checklist of plist, entitlement, URL scheme, framework and storage targets
- A ranked list of hook boundaries from request builder to gating selector
- A rule to patch pinning or environment checks only far enough to expose the real request path
- Evidence guidance covering class names, selectors, Keychain items and the smallest replayable request
Common Use Cases
- Recovering how an iOS app signs its requests in a CTF lab
- Inspecting Keychain entries and local plist state of a challenge app
- Analyzing deeplink and universal link handling in a test build
- Replaying an accepted request from hook output
What Makes It Unique
It aims hooks at the boundary that changes server acceptance, such as signers and trust evaluators, and warns against stopping at UI handlers. It also insists that static bundle evidence and live hook output agree before a trust path is called understood.
Under The Hood
The skill is instruction text only: the SKILL.md body, one reference checklist and a small agent config file that disables implicit invocation. It ships no scripts. The instructions describe Frida hooking, Keychain and plist inspection and pinning bypass that the agent is to carry out on an app and device the user supplies in a sandbox, and the agent would run those commands itself. The skill replies in Simplified Chinese unless asked for English and runs only after the orchestrator skill is active.