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 JustineDevs/premortem --skill ios-pentestgit clone --depth 1 https://github.com/JustineDevs/premortemWrote 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/justinedevs/premortem/ios-pentest)<a href="https://agentmods.dev/skills/justinedevs/premortem/ios-pentest"><img src="https://agentmods.dev/badge/skills/justinedevs/premortem/ios-pentest/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/justinedevs/premortem/ios-pentest"><img src="https://agentmods.dev/badge/skills/justinedevs/premortem/ios-pentest.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.00095 | $0.02452 |
| Opus 5 | $0.00048 | $0.01226 |
| Sonnet 5 | $0.00019 | $0.00490 |
| Haiku 4.5 | $0.00010 | $0.00245 |
Grade A, and why
ios-pentest 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 — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
iOS Mobile Application Penetration Testing
Thin router for an iOS app security assessment. Full OWASP MASTG coverage (recon → static → dynamic → network → storage → crypto → auth → reporting). Detailed runbooks live under workflows/ and methodology/; load them only when needed.
When to Use
- New iOS application security assessment (IPA + installed app).
- Bypass SSL pinning, jailbreak detection, biometric, anti-debug.
- Extract and triage keychain / NSUserDefaults / files / SQLite.
- Intercept and tamper HTTPS / gRPC / WebSocket traffic.
- OWASP MASTG / MASVS compliance testing.
- Analyze a decrypted or encrypted Mach-O binary.
Trigger Phrases
"pentest iOS app", "test this IPA", "bypass SSL pinning iPhone", "extract keychain", "MASTG iOS", "iOS jailbreak bypass", "analyze .ipa", "test iPhone app".
When NOT to Use This Skill
- Android APK analysis → use
android-pentest. - Generic web API testing for the backend → use
web-pentest/api-pentest. - iOS source-code review (you have the repo) → use
secure-code-reviewwith iOS language packs. - macOS desktop app analysis → use
macos-pentest.
Decision Tree
target acquired?
├── no binary yet → workflows/ipa_decryption.md
└── yes
├── need HTTPS visibility? → workflows/ssl_pinning_bypass.md
├── app exits on jailbroken device? → workflows/jailbreak_detection_bypass.md
├── hunting credentials/tokens? → workflows/keychain_extraction.md
├── testing login / biometric? → workflows/auth_testing.md
└── full engagement → workflows/complete_assessment.md
Parallelism Hints
Run concurrently (independent I/O, no shared state):
class-dump -H App.app/App -o headers/otool -L App.app/Appandotool -hv App.app/Appstrings -a App.app/App | grep ...plutil -p App.app/Info.plist- Objection enumeration in a separate spawn.
Must run sequentially (shared Frida session / spawn state):
- Frida
--no-pausespawn → wait for bypass script to land → drive app → then attach further scripts. - Objection
ios sslpinning disable→ then any traffic-dependent command. ideviceimagemounter→ thenfrida-ps -U.- Keychain dump requires app launched at least once post-install.
What ships with it
31 files 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.
- checklists/owasp_mastg_ios.md 6.7 KB
- examples/initial_setup.md 630 B
- examples/keychain_dump.md 767 B
- examples/ssl_bypass_run.md 649 B
- methodology/auth_testing.md 1.6 KB
- methodology/crypto_testing.md 1.3 KB
- methodology/data_storage.md 2.3 KB
- methodology/dynamic_analysis.md 1.4 KB
- methodology/network_testing.md 1.7 KB
- methodology/recon.md 1.2 KB
- methodology/static_analysis.md 1.5 KB
- payloads/jailbreak_detection_paths.txt 929 B
- payloads/url_scheme_tests.txt 3.6 KB
- references/bounty_patterns_2024_2026.md 7.0 KB
- references/frida_ios_snippets.md 6.8 KB
- references/ios_vulns.md 2.3 KB
- references/troubleshooting.md 1.6 KB
- schemas/finding.json 2.1 KB
- scripts/biometric_bypass.js 3.9 KB runs code
- scripts/crypto_hooks.js 8.7 KB runs code
- scripts/jailbreak_bypass.js 8.4 KB runs code
- scripts/keychain_hooks.js 7.0 KB runs code
- scripts/method_tracer.js 6.8 KB runs code
- scripts/ssl_pinning_bypass.js 5.9 KB runs code
- templates/finding_report.md 1.1 KB
- workflows/auth_testing.md 1.7 KB
- workflows/complete_assessment.md 2.1 KB
- workflows/ipa_decryption.md 1.4 KB
- workflows/jailbreak_detection_bypass.md 1.6 KB
- workflows/keychain_extraction.md 1.8 KB
- workflows/ssl_pinning_bypass.md 1.7 KB
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 · 169 lines · 95 tokens per session scan A 1c816d537317
ios-pentest is a skill published in the GitHub repository JustineDevs/premortem (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 95 tokens to every session and 2,452 once invoked, about $0.0005 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
agent-browser
Browser automation via Chrome/Chromium CDP — open, snapshot, click, screenshot. For testing web apps, mobile layouts, and automated interactions without Playwright/Puppeteer.
baguette
Drive iOS simulators programmatically via the baguette CLI — taps, swipes, multi-finger gestures, hardware buttons (Home / Lock / Volume / Action / Power), ASCII keyboard text, and frame capture, all without opening Xcode. Use when: (1) an agent needs to drive a booted iOS simulator from a script — tap a coordinate…
asc
Drive App Store Connect from the terminal with the asc CLI — TestFlight builds, groups, testers and What to Test notes; App Store versions, metadata, keywords, screenshots and release notes; submissions and review health; signing, provisioning and notarization; crash and beta-feedback triage; pricing, subscriptions…
native-app-profiling
Profile native macOS/iOS apps using Time Profiler via CLI (xctrace). Use when asked to identify performance hotspots, profile CPU usage, or diagnose slow code paths without opening Instruments.
performance-audit
Audit and improve SwiftUI runtime performance. Use for requests to diagnose slow rendering, janky scrolling, high CPU/memory usage, excessive view updates, or layout thrash in SwiftUI apps.
Debroid CLI Debugger
Orchestrate headless Android debugging via JDWP. ACTIVATE this skill whenever asked to debug an Android application, set line or exception breakpoints, inspect runtime variables or Jetpack Compose state, step through execution, evaluate live expressions, watch fields, or diagnose runtime crashes.