Skip to main content
skill CX Codex

competition-ios-runtime — Claude Code skill: what it does

competition-ios-runtime — a skill for Claude Code that automates iOS runtime analysis and hooking. It runs as a downstream module after $ctf-sandbox-orchestrator is active.

MIT 110 installs ★ 45,047 updated 2026-09-22

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add zhaoxuya520/reverse-skill --skill competition-ios-runtime -a claude-code
Open on GitHub

What competition-ios-runtime does

This skill performs IPA analysis, traces Objective-C or Swift method calls, and intercepts network requests. It facilitates SSL pinning bypass, Keychain inspection, and recovery of request-signing logic.

It requires an active $ctf-sandbox-orchestrator to establish the sandbox context. Without this orchestrator, the skill cannot access the necessary permissions or evidence priorities.

What it helps with

  • Hook Objective-C or Swift methods in iOS apps
  • Bypass SSL pinning for traffic analysis
  • Inspect Keychain data or Info.plist values
  • Recover request-signing logic

Example prompts for the agent

  • Analyze method calls in this IPA using competition-ios-runtime
  • Bypass SSL pinning and intercept app requests

How to install competition-ios-runtime

1Skills CLI (Vercel)

npx skills add zhaoxuya520/reverse-skill --skill competition-ios-runtime -a claude-code

2Manually: put the files in place

~/.claude/skills/competition-ios-runtime/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/competition-ios-runtime/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about competition-ios-runtime

How to install competition-ios-runtime in Claude Code?

Run npx skills add zhaoxuya520/reverse-skill --skill competition-ios-runtime -a claude-code.

What does this skill do?

It automates iOS app analysis, including Frida hooks, Keychain inspection, and request-signing recovery.

What is required to run it?

You must have $ctf-sandbox-orchestrator running, as this skill operates as its downstream module.

Source text

SKILL.md · MIT
---
name: competition-ios-runtime
description: 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 runtime behavior, inspect Keychain or plist state, bypass pinning, analyze deeplinks or universal links, or replay accepted iOS requests. Use only after `$ctf-sandbox-orchestrator` has already established sandbox assumptions and routed here.
---

# Competition iOS Runtime

Use this skill only as a downstream specialization after `$ctf-sandbox-orchestrator` is already active and has established sandbox assumptions, node ownership, and evidence priorities. If that has not happened yet, return to `$ctf-sandbox-orchestrator` first.

Use this skill when the decisive path runs through live iOS trust boundaries rather than static strings or plist values alone.

Reply in Simplified Chinese unless the user explicitly requests English.

## Quick Start

1. Preserve the original IPA, extracted bundle, and any decrypted or re-signed copy as separate artifacts.
2. Start with `Info.plist`, entitlements, URL schemes, frameworks, Keychain usage, and local app storage before broad runtime hooks.
3. Choose the narrowest runtime boundary that proves behavior: signer, trust evaluator, Keychain accessor, Objective-C or Swift method, or network request builder.
4. Correlate static bundle evidence and live hook output before claiming the trust path is understood.
5. Reproduce the accepted request, token, or gated branch from the smallest hook set.

## Workflow

### 1. Static iOS Triage

- Map bundle structure, `Info.plist`, entitlements, URL schemes, universal links, embedded frameworks, and app group paths.
- Record likely trust boundaries: request signers, device binding, certificate checks, jailbreak checks, Keychain access, or local cache loading.
- Note whether sensitive logic sits in Objective-C, Swift, embedded frameworks, or a bundled web surface.

### 2. Hook The Runtime Boundary

- Prefer hooking request builders, crypto helpers, trust evaluators, Keychain reads, or Objective-C selectors instead of broad UI handlers.
- Record plaintext inputs, headers, nonces, signed strings, and outputs at the boundary that changes server acceptance.
- Patch or bypass pinning or environment checks only enough to expose the real request path.

### 3. Replay The Accepted Path

- Rebuild the smallest stateful sequence: local token, device identifier, request body, signature, headers, and trust checks.
- Keep hook logs, bundle paths, plist keys, and local storage artifacts tied to the same session or account state.
- If the task becomes mostly about transform recovery instead of iOS runtime, switch back to the broader crypto or mobile skill.

## Read This Reference

- Load `references/ios-runtime.md` for hook targets, storage checklist, and evidence packaging.

## What To Preserve

- Bundle paths, entitlements, plist keys, selectors, class names, hook points, and header names
- Keychain items, local DB or plist paths, URL schemes, and app-group storage locations
- The smallest replayable request or branch that proves the iOS trust boundary

© zhaoxuya520 · MIT · zhaoxuya520/reverse-skill

Similar skills

All skills for Security →

From the same set36

The whole set →
competition-request-normalization-smuggling competition-request-normalization-smuggling is a Claude Code skill that analyzes HTTP parsing discrepancies between proxies and backend servers in CTF workflows. CX Codex +1 110installs competition-bundle-sourcemap-recovery The competition-bundle-sourcemap-recovery Claude Code skill reconstructs JavaScript structure from served assets and source maps. It runs after ctf-sandbox-orchestrator routes a task involving chunk loading or hidden routes. CX Codex +1 110installs competition-websocket-runtime competition-websocket-runtime is a Claude Code skill that inspects WebSocket and SSE handshakes, subscriptions, and frames after the orchestrator runs. CX Codex +1 110installs competition-stego-media The competition-stego-media Claude Code skill searches media files for hidden payloads in CTF tasks. It runs after ctf-sandbox-orchestrator routes an image, audio, video, or document for steganography analysis. CX Codex +1 110installs competition-graphql-rpc-drift competition-graphql-rpc-drift — a Claude Code skill compares GraphQL and RPC contracts with live handler behavior. It joins a CTF workflow after the main orchestrator sets up the sandbox. CX Codex +1 110installs competition-identity-windows competition-identity-windows — a skill for Claude Code and Codex that examines Active Directory attacks, Windows host artifacts, and CTF pivot chains. It runs after routing by $ctf-sandbox-orchestrator. CX Codex +1 109installs competition-agent-cloud The competition-agent-cloud Claude Code skill investigates agent and cloud paths in CTF sandboxes. It is routed in after the orchestrator sets the sandbox assumptions, for tracing input-to-tool actions or deployment behavior. CX Codex +1 109installs competition-browser-persistence competition-browser-persistence — a skill for Claude Code that investigates browser persistence surfaces in CTF sandboxes. It activates when stored client state alters request flows, rendering, or access rules. CX Codex +1 109installs

Project sponsors

Companies that keep this analytics open