hopper-debugger
Hopper debugging: macOS/iOS binaries, ObjC/Swift symbols, dyld, LLDB.
Skill by az9713
Install
Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.
npx agentmarket install skill/az9713-hopper-debugger
Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.
Get the weekly diff
The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.
About
Reviews
Write a reviewNo reviews yet. Installed it? Reviews come from verified installers only. How reviews work
Permissions: not checked yet.
What's inside
- Skill name
hopper-debugger- Description
- Hopper debugging: macOS/iOS binaries, ObjC/Swift symbols, dyld, LLDB.
- License
- MIT
- Instructions
- 130 lines in SKILL.md · view on GitHub
Files (2)
- SKILL.md
- openai.yaml · agents/
SKILL.md (first lines)
# Hopper Debugger Goal: use Hopper through `mcporter` as a queryable disassembler, then combine the result with local source, LLDB, logs, and focused repros. ## Quick Start Validate the MCP server: ```bash MCPORTER_LIST_TIMEOUT=15000 timeout 20 mcporter list hopper --brief ``` List open Hopper documents: ```bash MCPORTER_CALL_TIMEOUT=20000 timeout 30 mcporter call hopper.list_documents --output json ``` If no document is open, open the binary/framework in Hopper first: ```bash open -a "Hopper Disassembler" /path/to/Binary ``` Hopper may show a first-open/import dialog. Let the user click the confirmation button, then retry the MCP call. Avoid parallel Hopper MCP calls; the server can close the transport or crash Hopper while import is still settling. ## Apple Frameworks Prefer already extracted dyld-cache framework binaries when present: ```bash /tmp/dsc-appkit/System/Library/Frameworks/AppKit.framework/Versions/C/AppKit /tmp/dsc-appkit/System/Library/Frameworks/SwiftUI.framework/Versions/A/SwiftUI ``` Open one at a time when debugging SwiftUI/AppKit boundary issues: ```bash open -a "Hopper Disassembler" /tmp/dsc-appkit/System/Library/Frameworks/AppKit.framework/Versions/C/AppKit mcporter call hopper.list_documents --output json open -a "Hopper Disassembler" /tmp/dsc-appkit/System/Library/Frameworks/SwiftUI.framework/Versions/A/SwiftUI mcporter call hopper.list_documents --output json ``` Verify access: ```bash mcporter call hopper.list_documents --output json mcporter call hopper.current_document --output json mcporter call hopper.search_strings pattern=SwiftUI --output json mcporter call hopper.search_strings pattern=NSStatusItem --output json ``` Document names can start as `Untitled`; retry after Hopper finishes importing. Use `current_document`, symbol/string searches, and window title changes to identify AppKit vs SwiftUI. ## Query Workflow 1. Start from the local source path or runtime symbol you are trying to explain. 2. Search names/procedures/strings: ```bash mcporter call hopper.search_procedures pattern='NSStatusBar' --output json mcporter call hopper.search_name pattern='NSStatusBarButtonCell' --output json mcporter call hopper.search_strings pattern='NSStatusItem' --output json ``` 3. Inspect one small target at a time: ```bash mcporter call hopper.procedure_info procedure='<symbol>' --output json mcporter call hopper.procedure_assembly procedure='<symbol>' --output json mcporter call hopper.procedure_pseudo_code procedure='<symbol>' --output json mcporter call hopper.procedure_callers procedure='<symbol>' --output json mcporter call hopper.procedure_callees procedure='<symbol>' --output json mcporter call hopper.xrefs address=0x12345678 --output json ``` 4. Summarize the relevant control flow; do not paste large decompilations. 5. Validate the hypothesis with LLDB/logging/repro before editing app code. ## Status Item / Menu Click Bugs Useful AppKit/SwiftUI searches: ```bash mcporter call hopper.search_strings pattern='NSStatusItem_Private_ForSwiftUI' --output json mcporter call hopper.search_procedures pattern='popUpStatusBarMenu' --output json mcporter call hopper.search_procedures pattern='trackMouse' --output json mcporter call hopper.search_name pattern='NSStatusBarButtonCell' --output json mcporter call hopper.search_name pattern='NSStatusItem' --output json ``` Symbols worth inspecting when menu bar clicks do nothing: - `-[NSStatusBarButtonCell trackMouse:inRect:ofView:untilMouseUp:]` - `-[NSStatusBarButtonCell _sendActionFrom:]` - `-[NSStatusItem popUpStatusBarMenu:]` - `-[NSApplication sendAction:to:from:]` - SwiftUI status/menu symbols that reference `NSStatusItem_Private_ForSwiftUI` Compare disassembly against runtime state: ```bash pgrep -af "App.app/Contents/MacOS/App" lldb /path/to/debug/Binary ``` For hardened signed apps, attach may fail without `get-task-allow`; launch the raw debug binary under LLDB when needed. ## Failure Handling - Wrap Hopper calls with `timeout`; a modal/import or closed document can leave the transport stuck. - Do not send concurrent Hopper MCP requests during import. If a query is expensive, wait for it to finish before starting another. - If calls report `Connection closed`, check for a Hopper modal, then retry after confirmation. - If Hopper crashes, reopen a single document, wait for import/analysis, and re-run `list_documents` before deeper searches. - If mcporter is wedged, inspect processes before killing anything: ```bash
From az9713/agent_scripts_tutorial, MIT.
More from az9713/agent_scripts_tutorial
- 0.419score
github-project-triage
az9713
Use whenever the user types triage or asks to triage GitHub issues, PRs, queues, CI, blockers, risk, proof, or next actions.
SkillCFreshness: CClaude Code +9 - 0.414score
maintainer-orchestrator
az9713
Orchestrate delegated maintainer work across Peter-majority repositories: prepare decision-ready PRs, monitor workers, clear queues, and release.
SkillCFreshness: CClaude Code +9 - 0.412score
clickclack
az9713
ClickClack ops: chat app, Hetzner deploy, DNS/docs/app, Docker rollout.
SkillCFreshness: CClaude Code +9
Signals
- Stars
- 0
- Forks
- 0
- Open issues
- 0
- Last commit (this folder)
- Jun 13, 2026 (4 months ago)
From GitHub (fetched Oct 24, 2026).
Details
- License
- MIT
- Repository
- github.com/az9713/agent_scripts_tutorial
- First seen
- Oct 24, 2026
- Last checked
- Oct 24, 2026
- Source
- GitHubgithub-graphql
Same skill elsewhere
Copies of this SKILL.md published by others; search shows only one of them.
More from az9713
- 0.461score
codex-first
az9713
Claude Code-only work routing: delegate implementation, fixing, exploratory subagents, rebasing, and PR merging/landing to Codex CLI while Claude specifies…
SkillBFreshness: BClaude Code +9 - 0.430score
offer-shaper
az9713
Convert a vague AI idea or buyer pain into a concrete paid offer with buyer, promise, deliverable, price, proof mechanism, and sales path.
SkillCFreshness: C★ 1Claude Code +9 - 0.430score
context-reset
az9713
Preserve durable project state before clearing or compacting context so Claude Code can reset without losing business, technical, and verification state.
SkillCFreshness: C★ 1Claude Code +9 - 0.430score
break-test
az9713
Red-team a project, automation, app, or offer by trying to break it technically, commercially, operationally, and in front of a buyer.
SkillCFreshness: C★ 1Claude Code +9 - 0.430score
council-session
az9713
Run the full Idea-to-Capital council loop across buyer, CFO, technical, distribution, verification, and packaging perspectives.
SkillCFreshness: C★ 1Claude Code +9 - 0.430score
opportunity-triage
az9713
Evaluate an AI project, automation, SaaS, content product, or service idea for buyer demand, profitability, speed to validation, and whether to build…
SkillCFreshness: C★ 1Claude Code +9
Cite this page
hopper-debugger skill. Agent Mart. https://agentmart.dev/skills/az9713-hopper-debugger (last updated 2026-10-24)