Hopper debugger
A curated collection of agent skills for your AI agents - engineering craft, prompt engineering, design, growth marketing, ...
npx -y skills add mouadja02/skills --skill hopper-debuggerAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 8 stars8 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Hopper Disassembler debugging: macOS/iOS binaries, ObjC/Swift symbols, dyld, LLDB.
SKILL.md
3.1 KB, 711 tokens by cl100k_base, as published. Nobody here has run it
Hopper Debugger
Attribution: Sourced from steipete/agent-scripts by Peter Steinberger.
Goal: use Hopper through mcporter as a queryable disassembler, then combine the result with local source, LLDB, logs, and focused repros.
When to Use
- Reverse-engineering macOS/iOS binaries to understand private API behavior
- Debugging ObjC/Swift symbol resolution, dyld loading, or framework internals
- Investigating runtime crashes by inspecting disassembly and pseudo-code
- Querying Apple framework internals via Hopper + LLDB
Quick Start
Validate the MCP server:
MCPORTER_LIST_TIMEOUT=15000 timeout 20 mcporter list hopper --brief
List open Hopper documents:
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:
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 during import.
Apple Frameworks
Prefer already extracted dyld-cache framework binaries when present:
/tmp/dsc-appkit/System/Library/Frameworks/AppKit.framework/Versions/C/AppKit
/tmp/dsc-appkit/System/Library/Frameworks/SwiftUI.framework/Versions/A/SwiftUI
Query Workflow
- Start from the local source path or runtime symbol you are trying to explain.
- Search names/procedures/strings:
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
- Inspect one small target at a time:
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
- Summarize the relevant control flow; do not paste large decompilations.
- Validate the hypothesis with LLDB/logging/repro before editing app code.
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 calls report
Connection closed, check for a Hopper modal, then retry. - If Hopper crashes, reopen a single document, wait for import/analysis, and re-run
list_documents. - If mcporter is wedged:
pgrep -af 'mcporter|HopperMCPServer|Hopper Disassembler'
mcporter daemon stop
mcporter daemon start