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 skills add GDvega/super-android-kotlin-firebase-skill --skill debugginggit clone --depth 1 https://github.com/GDvega/super-android-kotlin-firebase-skillWrote 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/gdvega/super-android-kotlin-firebase-skill/debugging)<a href="https://agentmods.dev/skills/gdvega/super-android-kotlin-firebase-skill/debugging"><img src="https://agentmods.dev/badge/skills/gdvega/super-android-kotlin-firebase-skill/debugging/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.
<a href="https://agentmods.dev/skills/gdvega/super-android-kotlin-firebase-skill/debugging"><img src="https://agentmods.dev/badge/skills/gdvega/super-android-kotlin-firebase-skill/debugging.svg" alt="Reviewed on agentmods" width="80" 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.00037 | $0.00598 |
| Opus 5.5 | $0.00015 | $0.00239 |
| Sonnet 5.5 | $0.00007 | $0.00120 |
| Haiku 4.5 | $0.00004 | $0.00060 |
Grade A, and why
debugging 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.
How it starts
The opening of the file, as written. The whole thing — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Find root causes with evidence and apply minimal fixes.
When to use
- A build, sync, runtime crash or ANR occurs.
- Logcat, adb or Crashlytics evidence needs triage.
- A minimal reproduction is needed.
Inputs to inspect
- Exact command that failed.
- Full stacktrace and first error.
- Relevant Gradle versions and files.
- Reproduction steps and device/API.
Required workflow
- Separate first cause from downstream noise.
- Locate the file or config responsible.
- Apply one minimal fix.
- Re-run the failing command.
- Document remaining uncertainty and next diagnostic step.
Rules
- Do not shotgun-update dependencies.
- Do not delete caches as the main solution.
- Do not silence warnings that indicate real incompatibility.
- Preserve crash evidence.
- Mention local-only issues separately.
Related existing skills
Local skills to invoke
- gradle-build
- testing
- firebase-crashlytics-analytics
- code-review-refactor
External companion skills to use when installed
Do not assume these companion skills are installed. Prefer the local skills above first, then consult Companion Skills for install and verification commands.
- skydoves/android-testing-skills — use for deeper Android or Compose UI testing, semantics, assertions or test workflow guidance.
Files commonly touched
build.gradle.ktsGradle logsLogcat outputCrashlytics reportssource file in stacktrace
Commands to validate
./gradlew --stacktrace <task>
./gradlew build --scan
adb logcat
adb bugreport
./gradlew test
Common mistakes to avoid
- Fixing the last error instead of the first cause.
- Changing many versions at once.
- Ignoring device/API-specific reproduction.
- Removing code without explaining risk.
Checklist
- First cause identified.
- Minimal fix proposed.
- Verification command given.
- Reproduction documented.
- Risk/rollback noted.
Example prompts
- Use $super-android-kotlin-firebase to debug this Gradle error.
- Use $super-android-kotlin-firebase to triage this Crashlytics stacktrace.
What ships with it
2 files 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.
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 · 101 lines · 37 tokens per session scan A fbb7074b36ed
debugging is a skill published in the GitHub repository GDvega/super-android-kotlin-firebase-skill (2 stars, last pushed 4mo ago), licensed MIT. It adds 37 tokens to every session and 598 once invoked, about $0.0001 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-31.
Other skills, from other repositories
argent-metro-debugger
Debug a JS runtime via CDP using argent debugger tools. Primary path is React Native via Metro (iOS / Android / Vega); a subset of the tools (debugger-connect, debugger-status, debugger-evaluate, debugger-log-registry) also drive a Chromium (CDP) app's renderer (an Electron app, or any Chromium browser exposing CDP)…
argent-react-native-optimization
Optimizes a React Native app by profiling first to find real bottlenecks, then sweeping for mechanical issues. Entry-point for all performance work. Use when the app feels slow, user asks to optimize, fix re-renders, reduce jank, or improve startup. Delegates to argent-react-native-profiler for measurement.
nightly-audit-engineer-getting-started
A first-conversation guide for setting up a code-audit assistant. A code audit is a focused review of source code for defects or risky behavior, with the needed repository, scope, concerns, permissions, and schedule clarified first.
nightly-audit-engineer-ops
A workflow for reviewing code for reproducible quality problems and recording the evidence behind each finding. It follows data through inputs, permissions, storage, asynchronous work, and recovery, then suggests the smallest authorized fix.
nightly-audit-engineer-evidence
A small local checker that creates stable identifiers for code-audit findings and marks duplicates within the current batch or among previously seen findings. It processes supplied JSON with Python and does not infer whether a problem was fixed.
argent-native-profiler
Native profiling for CPU hotspots, UI hangs, memory issues. iOS via xctrace; Android via Perfetto. Use when diagnosing native-level performance issues.