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/jubakitiashvili/everything-react-native-expo/debugnpx skills add JubaKitiashvili/everything-react-native-expo --skill debuggit clone --depth 1 https://github.com/JubaKitiashvili/everything-react-native-expoWrote 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/jubakitiashvili/everything-react-native-expo/debug)<a href="https://agentmods.dev/skills/jubakitiashvili/everything-react-native-expo/debug"><img src="https://agentmods.dev/badge/skills/jubakitiashvili/everything-react-native-expo/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.1 | $0.00013 | $0.00447 |
| Opus 5 | $0.00006 | $0.00224 |
| Sonnet 5 | $0.00003 | $0.00089 |
| Haiku 4.5 | $0.00001 | $0.00045 |
Grade A, and why
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 6d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- erne-debug — 91% identical, 8 lines differ
What it actually says
/debug — Systematic Diagnosis
You are executing the /debug command. Use the performance-profiler agent for systematic bug diagnosis.
Process
Step 1: Reproduce
Define exact reproduction steps:
- Starting state
- Actions taken
- Expected behavior
- Actual behavior
- Environment (device, OS, Expo SDK version)
Step 2: Classify the Bug
| Category | Indicators | First Check |
|---|---|---|
| Crash | App terminates | Check Metro logs, Hermes stack trace |
| Render | Visual glitch, wrong layout | Check component tree, re-render count |
| State | Wrong data displayed | Check Zustand store, TanStack Query cache |
| Navigation | Wrong screen, broken back | Check Expo Router history, params |
| Performance | Jank, slow response | Check FPS, bundle size, memory |
| Network | Failed API calls | Check request/response, auth tokens |
| Native | Platform-specific issue | Check native logs (Xcode/Logcat) |
Step 3: Investigate
JavaScript layer:
# Check Metro bundler logs
# Search for errors/warnings in console output
# Add strategic console.log at suspected points
React layer:
- Component re-render tracking (React DevTools)
- Props/state inspection
- Effect dependency analysis
Native layer (if agent-device available):
- Screenshot current state
- Navigate through repro steps visually
- Capture native crash logs
Step 4: Fix & Verify
- Identify root cause
- Implement minimal fix
- Verify fix resolves the issue
- Check for regression (run related tests)
- Document what caused it and why
Output
## Bug Report
### Summary
[One-line description]
### Root Cause
[Technical explanation]
### Fix Applied
[Files changed with explanation]
### Verification
[Steps taken to verify fix]
[Test results]
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.
- 6d ago First seen · 75 lines · 13 tokens per session scan A 0ff9121f7a6c
debug is a skill published in the GitHub repository JubaKitiashvili/everything-react-native-expo (44 stars, last pushed 5mo ago), licensed MIT. It adds 13 tokens to every session and 447 once invoked, about $0.0001 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-30.
Other skills, from other repositories
ios-fix
Autonomous iOS bug fixer. (gstack).
flutter-pr-checks-finder
Find failing checks on a Flutter PR and locate the corresponding LUCI log URLs.
analyze-github-flake
Expertise in analyzing flake github issues in the flutter/flutter repository. Use when a user wants to analyze the flakiness of a specific link to a flutter github issue.
google-mobile-ads-validate
Validates a project's Google Mobile Ads (GMA) SDK integration for iOS, Android, or Unity projects. Use when conducting a full pre-launch audit of an app that integrates GMA SDK or when validating any individual GMA SDK integration checks, such as when validating ad unit IDs and ad formats, SKAdNetwork IDs, mediation…
competition-ios-runtime
Internal downstream skill for ctf-sandbox-orchestrator. CTF-sandbox workflow for IPA runtime analysis, Frida hooks, Objective-C or Swift method tracing, Keychain inspection, SSL pinning bypass, URL scheme handling, and iOS request-signing recovery. Use when the user asks to hook an IPA, trace Objective-C or Swift…
ios-debugger-agent
Build, launch, inspect, and drive iOS apps with the repository-configured XcodeBuildMCP server. Use on macOS for iOS Simulator builds, focused native test runs, semantic UI automation, screenshots, logs, or debugging, including T3 Code Mobile verification.