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 artemnovichkov/skills --skill crashlyticsgit clone --depth 1 https://github.com/artemnovichkov/skillsWrote 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/artemnovichkov/skills/crashlytics)<a href="https://agentmods.dev/skills/artemnovichkov/skills/crashlytics"><img src="https://agentmods.dev/badge/skills/artemnovichkov/skills/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/artemnovichkov/skills/crashlytics"><img src="https://agentmods.dev/badge/skills/artemnovichkov/skills/crashlytics.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.00045 | $0.00653 |
| Opus 5 | $0.00023 | $0.00327 |
| Sonnet 5 | $0.00009 | $0.00131 |
| Haiku 4.5 | $0.00005 | $0.00065 |
Grade A, and why
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 11d 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Crashlytics
Generate crash reports from Firebase Crashlytics for iOS and Android with automated fix proposals and developer assignments.
When to Use
- User asks to analyze crashes or crash reports
- User wants to triage production issues from Crashlytics
- User asks for crash severity analysis or fix proposals
- User mentions Firebase Crashlytics
Commands
/crash-report
Analyzes Crashlytics crashes and generates a triage report. See commands/crash-report.md for the full workflow, platform-specific analysis rules, and error handling.
Process:
- Validate Firebase MCP server connection (test with a simple query first)
- Fetch fatal errors from Crashlytics with stack traces and occurrence counts
- Launch subagents for deep analysis of each crash (max 10 concurrent)
- Extract stack traces, search codebase for crash locations
- Identify root causes and calculate severity scores
- Propose fixes with before/after code snippets
- Use git blame to assign developers
- Generate
crash-report-[YYYY-MM-DD].md
If validation fails (MCP unavailable, no crashes found, auth error), the command file includes specific recovery steps for each scenario.
Example Output Structure
## Critical Issues (Score > 70)
### NullPointerException in CheckoutViewModel.kt:142
- **Severity**: 85/100 | **Count**: 1,247 | **Trend**: ↑
- **Root cause**: Force-unwrap on nullable payment response
- **Assigned**: @developer (last modified 2025-03-10)
- **Fix**: Replace `!!` with safe call + fallback
Requirements
- Firebase project with Crashlytics enabled
- Git repository
- MCP server config (
.mcp.jsonincluded in this skill)
MCP Server Setup
This skill bundles .mcp.json with the Firebase Crashlytics MCP server:
{
"mcpServers": {
"firebase": {
"command": "npx",
"args": ["-y", "firebase-tools@latest", "experimental:mcp", "--only", "crashlytics"]
}
}
}
Severity Score
| Factor | Weight | High Example | Low Example |
|---|---|---|---|
| Crash frequency | 40% | 1000+ occurrences | < 10 occurrences |
| Affected users | 30% | Wide user base | Single device |
| Pattern criticality | 30% | Memory / data loss | UI glitch |
What ships with it
4 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.
- 11d ago First seen · 83 lines · 45 tokens per session scan A 04f0b86c48f3
crashlytics is a skill published in the GitHub repository artemnovichkov/skills (36 stars, last pushed 3d ago), licensed MIT. It adds 45 tokens to every session and 653 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
audit-dead-code
Hunt dead code across a whole repository through four labelled lanes of unequal confidence. Knip (TS/JS unused files, exports, types, enum members), vulture (Python symbols), gopls (Go unexported symbols), and a portable grep lane (shell and other symbol languages), then adjudicate every candidate against the…
ci-log-interpretation
Use this skill when reading or analyzing CI logs from a Shopware GitHub Actions workflow to figure out why a build failed — phrases like "why did CI fail", "what broke the build", "check the pipeline", "interpret these logs", "debug this red build" — or whenever raw run logs, job logs, or check annotations from a…
devils-advocate
Stress-test plans and proposals via systematic adversarial review. Assumption extraction, evidence check, failure scenarios, operational gotchas. Before implementation begins. Use when: asked to attack a plan or proposal ('devil's advocate', 'stress test', 'poke holes', 'what could go wrong'), or before implementation…
reduce
Iteratively reduce coupling at any altitude — documents, code modules, applications, or repositories: scan for change-transmitting dependencies typed against a coupling model, verify each finding, apply a budgeted batch of safe behavior-preserving reductions, and ledger structural candidates for design routing so…
write
Produce a structured 5-field bug report (title, steps to reproduce, expected vs actual, severity with justification, suggested fix location) from an informal description. Read-only, never modifies code, never opens PRs, never files issues by default. Use when the user names a defect they observed ('there is a bug in…
known-issues
Looks up and tracks known Claude product issues. Searches known GitHub bugs, checks service health and model quality, and maintains a persistent registry of tracked issues. Use when: 'is this broken', 'known CC bugs', 'troubleshoot Claude Code', 'any workarounds', 'feature behaves unexpectedly', 'scan repo for…