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 commands/ivanlutsenko/awac-ai-agent-plugins/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/commands/ivanlutsenko/awac-ai-agent-plugins/crash-config)<a href="https://agentmods.dev/commands/ivanlutsenko/awac-ai-agent-plugins/crash-config"><img src="https://agentmods.dev/badge/commands/ivanlutsenko/awac-ai-agent-plugins/crash-config.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.00018 | $0.01298 |
| Opus 5 | $0.00009 | $0.00649 |
| Sonnet 5 | $0.00004 | $0.00260 |
| Haiku 4.5 | $0.00002 | $0.00130 |
Grade A, and why
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 5d 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 — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.
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.
- 5d ago First seen · 176 lines · 18 tokens per session scan A 4d08fb25d3f6
crash-config is a command published in the GitHub repository IvanLutsenko/awac-ai-agent-plugins (2 stars, last pushed 2d ago), licensed MIT. It adds 18 tokens to every session and 1,298 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-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
constitution
Create or update the project constitution from interactive or provided principle inputs.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.