A developer-only menu inside an iOS or macOS app for inspecting and changing diagnostic settings during development. It is included only in DEBUG builds, so it is excluded from production builds.

Use it to add a debug panel, developer tools menu, hidden tap or shake-to-debug access, environment switching, feature toggles, cache controls, and diagnostic tools.

It gives developers one place to test feature flags, switch between environments, inspect network logs, clear caches, trigger crashes, and export diagnostic information. This makes testing and troubleshooting easier during development.

debug-menu — Skill for Claude Code by rshankras

Install

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.

Any agent

npx skills add rshankras/claude-code-apple-skills --skill debug-menu

Clone the repo

git clone --depth 1 https://github.com/rshankras/claude-code-apple-skills

Made for: Claude Code.

Or install apple-skills, the plugin that ships this one along with the rest of its 147 skills.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/rshankras/claude-code-apple-skills/debug-menu/github.svg)](https://agentmods.dev/skills/rshankras/claude-code-apple-skills/debug-menu)

Your own site

<a href="https://agentmods.dev/skills/rshankras/claude-code-apple-skills/debug-menu"><img src="https://agentmods.dev/badge/skills/rshankras/claude-code-apple-skills/debug-menu/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/rshankras/claude-code-apple-skills/debug-menu"><img src="https://agentmods.dev/badge/skills/rshankras/claude-code-apple-skills/debug-menu.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 57 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 2,222 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

NVIDIA SkillSpector warn 7 Sept 2026

SkillSpector: 1 finding, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

medium Data Exfiltration · line 206
Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.

Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

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.00057	$0.02222
Opus 5.5	$0.00023	$0.00889
Sonnet 5.5	$0.00011	$0.00444
Haiku 4.5	$0.00006	$0.00222

Measured 1mo ago against content hash 70e7b6c30e8f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

debug-menu 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 1mo 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.

skills/generators/debug-menu/SKILL.md · 281 lines

How it starts

The opening of the file, as written. The whole thing — 281 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Generate a comprehensive developer debug menu accessible via shake gesture or hidden tap. Includes feature flag toggles, environment switching, network log viewer, cache clearing, crash trigger, and diagnostic info export. All code is wrapped in #if DEBUG so it never ships to production.

When This Skill Activates

Use this skill when the user:

Asks for a "debug menu" or "developer menu"
Wants "dev tools" or a "debug panel"
Mentions "shake to debug" or "diagnostic menu"
Wants to "toggle feature flags" from the app
Asks about "environment switching" (dev/staging/production)
Wants a "network log viewer" in the app

Pre-Generation Checks

1. Project Context Detection

Check deployment target (iOS 17+ / macOS 14+ required for @Observable)
Check Swift version (requires Swift 5.9+)
Identify source file locations and project structure

2. Conflict Detection

Search for existing debug/dev menu code:

Glob: **/*Debug*Menu*.swift, **/*DevMenu*.swift, **/*DevTools*.swift, **/*DebugPanel*.swift
Grep: "DebugMenu" or "DevMenu" or "motionEnded" or "shake" in *.swift

If existing debug menu found:

Ask if user wants to replace or extend it
If extending, integrate new sections into existing structure

3. Feature Flags Detection

Search for existing feature flag setup:

Glob: **/*FeatureFlag*.swift, **/*Feature*Toggle*.swift
Grep: "FeatureFlag" or "featureFlag" or "isFeatureEnabled"

If found, integrate debug menu toggles with existing feature flag system rather than creating a new one.

Configuration Questions

Ask user via AskUserQuestion:

Access method?
- Shake gesture (shake device to open)
- Hidden tap (5-tap on a hidden area)
- Both (shake + hidden tap) -- recommended
Sections to include? (multi-select)
- Feature flags (toggle flags on/off at runtime)
- Environment switcher (dev / staging / production)
- Network logs (recent requests with status codes and timing)
- Cache tools (clear image cache, HTTP cache, all caches)
- Crash trigger (force crash for Crashlytics testing)
- Diagnostics (device info, memory, disk, app version)

Read the full file on GitHub · 281 lines

Files

What ships with it

1 file 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.

templates.md 30 KB

Changes

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.

1mo ago First seen · 281 lines · 57 tokens per session scan A 70e7b6c30e8f

Subscribe to this mod's changes

debug-menu is a skill published in the GitHub repository rshankras/claude-code-apple-skills (816 stars, last pushed 2mo ago), licensed MIT. It adds 57 tokens to every session and 2,222 once invoked, about $0.0002 per session on Opus 5.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-08-30.

Debugging agent-skills ai-tools anthropic app-store apple aso

monitoring-observability

OpenTelemetry, structured logging, distributed tracing, alerting, and dashboards. Use when instrumenting services, designing logs/traces/metrics, defining SLOs and alerts, or debugging production behavior from telemetry.

travisjneuman/.claude · 48 tokens

thinking-scientific-method

When a symptom has several plausible causes, rank falsifiable hypotheses and run the cheapest discriminating observation first; prefer least-assumptive survivors only after evidence fit.

tjboudreaux/cc-thinking-skills · 38 tokens

thinking-five-whys-plus

When a fault is localized and the proximate cause is known but the systemic root is not, chain evidence-linked whys with a counterfactual stop and a countermeasure.

tjboudreaux/cc-thinking-skills · 41 tokens

thinking-map-territory

When a claim, doc, test, metric, or assumption conflicts with observed behavior, stop theorizing from the map and verify the live code or data; let territory overrule.

tjboudreaux/cc-thinking-skills · 42 tokens

debug-systematic

Systematic 4-phase debugging methodology for complex, intermittent, or mysterious issues. Use when investigating bugs, race conditions, or unexplained failures.

travisjneuman/.claude · 33 tokens

windows-ops

Comprehensive Windows workstation operations - diagnose slow boot, failing drives, BSOD crashes, startup bloat, runaway processes, event logs. Use for: Windows is slow, slow bootup, won't boot, blue screen, BSOD, kernel crash, drive failing, SMART errors, disk errors, Event 41, Event 129, storahci reset, BugCheck…

0xDarkMatter/claude-mods · 233 tokens

debug-menu