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 ArisGuimera/MobiAI-Core --skill mobiai-crashlyticsgit clone --depth 1 https://github.com/ArisGuimera/MobiAI-CoreWrote 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/arisguimera/mobiai-core/mobiai-crashlytics)<a href="https://agentmods.dev/skills/arisguimera/mobiai-core/mobiai-crashlytics"><img src="https://agentmods.dev/badge/skills/arisguimera/mobiai-core/mobiai-crashlytics/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/arisguimera/mobiai-core/mobiai-crashlytics"><img src="https://agentmods.dev/badge/skills/arisguimera/mobiai-core/mobiai-crashlytics.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00035 | $0.01027 |
| Opus 5 | $0.00017 | $0.00513 |
| Sonnet 5 | $0.00007 | $0.00205 |
| Haiku 4.5 | $0.00003 | $0.00103 |
Grade A, and why
mobiai-crashlytics 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 13d 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 — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Crashlytics Investigation
Deep investigation of a crash reported through Firebase Crashlytics. Goes beyond a raw stack trace — uses Crashlytics data to understand the full context: user journey, breadcrumbs, affected versions, device info, and event frequency.
When to Use
- User shares a Crashlytics link, crash ID, or issue title
- User asks to investigate a specific Crashlytics issue
- User mentions Firebase crashes or production crash reports from Crashlytics
Prerequisites
This skill requires access to Firebase Crashlytics data. Check what tools are available:
- Firebase MCP tools — if the Firebase MCP server is configured, use these tools:
firebase_update_environment— set the active Firebase project before queryingfirebase_list_apps— get the app IDs for the projectcrashlytics_get_issue— fetch issue metadata: event count, user count, error type. Parameters:appId,issueIdcrashlytics_list_events— fetch crash events with full stack traces. Parameters:appId,issueId,pageSize
- Firebase CLI —
firebase crashlytics:listand related commands - User provides the data — if no tools are available, ask the user to paste or export the crash details from the Crashlytics console
If none of these are available, fall back to the mobiai-analyze-crash skill with whatever information the user can provide manually.
Workflow
Step 1: Fetch Crash Details
Get the full crash information from Crashlytics:
- Stack trace — the complete symbolicated stack trace, not just the top frame
- Event count — how many times this crash has occurred
- Affected users — how many unique users have been affected
- Affected versions — which app versions are seeing this crash
- First seen / last seen — when did it start and is it still happening?
- Device breakdown — which devices and OS versions are most affected
Step 2: Analyze the User Journey
Crashlytics provides breadcrumbs — the sequence of events before the crash:
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.
- 13d ago First seen · 94 lines · 35 tokens per session scan A aaa1a683d49b
mobiai-crashlytics is a skill published in the GitHub repository ArisGuimera/MobiAI-Core (453 stars, last pushed 5d ago), licensed MIT. It adds 35 tokens to every session and 1,027 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-30.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.