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 IvanLutsenko/awac-ai-agent-plugins --skill crash-configgit clone --depth 1 https://github.com/IvanLutsenko/awac-ai-agent-pluginsWrote 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/ivanlutsenko/awac-ai-agent-plugins/crash-config)<a href="https://agentmods.dev/skills/ivanlutsenko/awac-ai-agent-plugins/crash-config"><img src="https://agentmods.dev/badge/skills/ivanlutsenko/awac-ai-agent-plugins/crash-config/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/ivanlutsenko/awac-ai-agent-plugins/crash-config"><img src="https://agentmods.dev/badge/skills/ivanlutsenko/awac-ai-agent-plugins/crash-config.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.00036 | $0.01400 |
| Opus 5.5 | $0.00014 | $0.00560 |
| Sonnet 5.5 | $0.00007 | $0.00280 |
| Haiku 4.5 | $0.00004 | $0.00140 |
Grade A, and why
crashlytics-crash-config 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 9d 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 — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Converted from Claude Code command
/crash-config. Review and adapt: hooks and MCP tool IDs may need manual mapping for Codex.
Crashlytics Plugin Configuration
Interactive setup for the Crashlytics plugin. Reads the current config (if exists), lets the user change settings via interactive prompts, and writes the result.
Step 0: Read current config
1. Check if config exists:
Read: .claude/crashlytics.local.md
2. If exists → parse YAML frontmatter, use current values as defaults
3. If not exists → use these defaults:
language: en
default_branch: master # local branch name; plugin uses origin/<this> for git blame
default_platform: android
forensics_model: opus
output_format: both
firebase_project_id: ""
firebase_app_id_android: ""
firebase_app_id_ios: ""
Step 1: Ask core settings
Use a single AskUserQuestion call with up to 4 questions:
AskUserQuestion:
questions:
- question: "What language should crash reports be written in?"
header: "Language"
options:
- label: "English"
description: "Reports in English (default)"
- label: "Russian"
description: "Reports in Russian (Русский)"
- label: "Other"
description: "Any other language of your choice"
multiSelect: false
- question: "Which branch should be used for git blame analysis?"
header: "Branch"
options:
- label: "master"
description: "Use master branch (default)"
- label: "main"
description: "Use main branch"
- label: "develop"
description: "Use develop branch"
- label: "Other"
description: "Any other branch of your choice"
multiSelect: false
- question: "What is your default platform?"
header: "Platform"
options:
- label: "Android"
description: "Android (Kotlin/Java) — default"
- label: "iOS"
description: "iOS (Swift/Objective-C)"
multiSelect: false
- question: "Which model should the forensics agent use?"
header: "Model"
options:
- label: "Opus (Recommended)"
description: "Deepest analysis, best for complex crashes"
- label: "Sonnet"
description: "Faster, good for most crashes"
- label: "Haiku"
description: "Fastest and cheapest, although weakest analysis"
multiSelect: false
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.
- 9d ago Changed · +4 lines dece3701152b
- 1mo ago First seen · 180 lines · 36 tokens per session scan A c5d0f9a5765d
crashlytics-crash-config is a skill published in the GitHub repository IvanLutsenko/awac-ai-agent-plugins (3 stars, last pushed 5d ago), licensed MIT. It adds 36 tokens to every session and 1,400 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-09-05.
Other skills, from other repositories
ios-fix
Autonomous iOS bug fixer. (gstack).
node-connect
Diagnose OpenClaw Control UI browser and native Android, iOS, or macOS node connection failures across route, auth, pairing, QR/setup-code, and reconnect states.
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…
jetpack-compose-performance
Diagnose and optimize Android Jetpack Compose UI code. Use this skill when analyzing performance bottlenecks of existing code to minimize recomposition overhead and prevent dropped frames and UI lag.
swiftui-performance-audit
SwiftUI performance: render, scroll, CPU/memory, updates, layout, Instruments.
android-tombstone-symbolication
Symbolicate the .NET runtime frames in an Android tombstone file. Extracts BuildIds and PC offsets from the native backtrace, downloads debug symbols from the Microsoft symbol server, and runs llvm-symbolizer to produce function names with source file and line numbers. USE FOR triaging a .NET MAUI or Mono Android app…