ios-simulator-debugger — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited ios-simulator-debugger (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
Before invoking Apple-only binaries, confirm the execution context is macOS. From Windows or Linux, run those steps in a Mac SSH project or through an already configured remote transport; do not retry missing Apple binaries locally.
Use the configured XcodeBuildMCP transport for simulator control, build/run, UI inspection, screenshots, interaction, and logs. Tool namespaces vary by agent, so the names below are the canonical XcodeBuildMCP tool names.
If the user should see or interact with the running app, prefer ios-simulator-browser after this skill has selected or launched the Simulator. Keep this skill focused on build/run, logs, bundle IDs, UI tree inspection, and headless simulator automation.
session_show_defaults before the first build, run, or test operation.list_sims. If none is booted, ask the user to boot one unless they asked you to boot it.session_set_defaults: projectPath or workspacePath, scheme, simulatorId, optional configuration: "Debug" and useLatestOS: true.build_run_sim when requested. If the build fails, inspect output and retry only when justified, optionally with preferXcodebuild: true.snapshot_ui or screenshot before UI interaction.launch_app_sim. If bundle id is unknown, call get_sim_app_path then get_app_bundle_id.snapshot_ui.id or label first; coordinates only when needed.type_text.gesture for scrolls and edge swipes.screenshot.Use build_run_sim or launch_app_sim; current XcodeBuildMCP releases capture runtime logs automatically and return the log path in the structured result. Read that returned file and summarize important lines. Relaunch through the same tool when fresh console output is required.
Wrong app means verify scheme/bundle id. Non-hittable elements require a fresh snapshot_ui after layout changes. Do not keep interacting after an unhandled build or launch failure.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.