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 agentmods add skills/hoainho/podium-mcp/rn-debugnpx skills add hoainho/podium-mcp --skill rn-debuggit clone --depth 1 https://github.com/hoainho/podium-mcpWrote 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/hoainho/podium-mcp/rn-debug)<a href="https://agentmods.dev/skills/hoainho/podium-mcp/rn-debug"><img src="https://agentmods.dev/badge/skills/hoainho/podium-mcp/rn-debug.svg" alt="Measured on agentmods" 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 | $0.00036 | $0.00303 |
| Opus 5 | $0.00018 | $0.00151 |
| Sonnet 5 | $0.00007 | $0.00061 |
| Haiku 4.5 | $0.00004 | $0.00030 |
Grade A, and why
rn-debug 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 5d 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.
What it actually says
Parse $ARGUMENTS as optional <UDID> and <action> (logs | apps | crash | all). Default action is all.
apps — find connected RN bundles:
Call metro_apps (port 8081). List each app with its title and webSocketDebuggerUrl. If Metro is not running, tell the user to start it first (npx react-native start).
logs — stream Metro console output:
Call metro_logs (durationMs 8000, maxLogs 150). Group output by level: log, warn, error. Highlight any exceptions or unhandled promise rejections.
crash — recent crash reports:
If UDID provided, call crash_list (udid UDID, sinceHours 48). Show entries newest-first with date, source (host/simulator), and one-line summary. For the most recent entry, call crash_get and summarize the exception type, termination reason, and top 5 frames.
all — run apps + logs + crash in sequence.
After gathering data, provide a structured diagnosis:
- What is running / not running
- Any errors or warnings
- Most likely root cause (if determinable)
- Suggested next step
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.
- 5d ago First seen · 23 lines · 36 tokens per session scan A 0f3ed9995211
rn-debug is a skill published in the GitHub repository hoainho/podium-mcp (4 stars, last pushed 2mo ago), licensed MIT. It adds 36 tokens to every session and 303 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
xcodebuildmcp-cli
Official skill for the XcodeBuildMCP CLI. Use when doing iOS/macOS/watchOS/tvOS/visionOS work (build, test, run, debug, log, UI automation).
xcodebuildmcp
Official skill for XcodeBuildMCP. Use when doing iOS/macOS/watchOS/tvOS/visionOS work (build, test, run, debug, log, UI automation).
sim-use
Drive iOS Simulator, Android emulator/device, and physical iPhone/iPad screens for AI agents. Use when asked to automate a simulator or emulator, drive a real iOS device, tap/swipe/type on a device, describe UI, take a screenshot, or interact with a mobile app.
app-store-preflight-compliance
Pre-submission compliance scanner workflow for Apple App Store apps. Use when reviewing iOS, macOS, tvOS, watchOS, or visionOS projects (Swift, Objective-C, React Native, Expo) for App Store rejection risks, submission readiness, privacy compliance, or guideline violations.
rozenite
Use Rozenite for Agents to inspect React Native DevTools data and Rozenite plugins on a live app target, either through shell-driven rozenite agent commands or programmatic @rozenite/agent-sdk usage. Trigger this skill for any task that needs live app inspection, debugging, or plugin interaction through Rozenite.
deep-links
Deep links in ToolHive Studio. Use when implementing, debugging, or asking about deep link features (toolhive-gui:// protocol), adding new deep link intents, understanding the deep link architecture, IPC model, or platform/packaging support.