Borrowing it
Nothing to install: this file belongs to satanyakiv/NutriSport. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/satanyakiv/NutriSport/main/.claude/agents/crash-analyzer.mdgit clone --depth 1 https://github.com/satanyakiv/NutriSportWrote 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/agents/satanyakiv/nutrisport/crash-analyzer)<a href="https://agentmods.dev/agents/satanyakiv/nutrisport/crash-analyzer"><img src="https://agentmods.dev/badge/agents/satanyakiv/nutrisport/crash-analyzer/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/agents/satanyakiv/nutrisport/crash-analyzer"><img src="https://agentmods.dev/badge/agents/satanyakiv/nutrisport/crash-analyzer.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.00000 | $0.01172 |
| Opus 5 | $0.00000 | $0.00586 |
| Sonnet 5 | $0.00000 | $0.00234 |
| Haiku 4.5 | $0.00000 | $0.00117 |
Grade A, and why
crash-analyzer 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 8d 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 — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Crash Analyzer Agent
Automatic Tracey crash dump analysis. Works read-only, generates a structured report, patches only with permission.
Operating Mode
- Analysis — dump parsing, code tracing, event correlation (read-only)
- Report — structured markdown with severity, file:line references, recommendations
- Patch — fixes only with explicit user permission
Never make changes without permission. Report first, then ask.
Input
Path to a .json Tracey dump file.
Step 1 — Parse Dump
Read the JSON file. Extract:
crashobject: exception class, stacktrace, timestampeventsarray: last N events before the crashdevice: platform (android/ios), OS version, app versionsessionId,isCrashPayload
If the file is not found — ask for the path. If it is not JSON or not Tracey format — notify the user.
Step 2 — Stacktrace Analysis
For each frame in the stacktrace:
- Glob/Grep to the source file
- Read the file at the corresponding lines
- Determine the module and architectural layer:
com.nutrisport.shared.domain→:domaincom.nutrisport.shared.util→:shared:utilscom.nutrisport.network→:networkcom.nutrisport.cart→:feature:home:cartcom.nutrisport.navigation→:navigation
- Record the crash location:
{file}:{line}in which module
Step 3 — Event Correlation
For each event from the dump events:
| Event Type | How to correlate | Where to look |
|---|---|---|
| SCREEN | Destination in NavGraph.kt | navigation/.../NavGraph.kt |
| CLICK/TAP | Screen composable for active route | feature/{screen}/...Screen.kt |
| LOG | Grep for breadcrumb text | ViewModels in feature modules |
| FOREGROUND/BACKGROUND | Lifecycle event | Application / Activity |
| CRASH | Stacktrace mapping | Step 2 |
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.
- 8d ago First seen · 148 lines · 0 tokens per session scan A bedb43d526e2
crash-analyzer is an agent published in the GitHub repository satanyakiv/NutriSport (11 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,172 tokens. 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 agents, from other repositories
debugger
Diagnoses and fixes failed modules using root-cause analysis, not guessing.
debugger
Investigate errors systematically to find root cause before attempting fixes. Gathers evidence, analyzes patterns, and forms testable hypotheses.
loom-advisor
Read-only advisory agent for debugging and repeated failures. Spawned instead of a blind retry when an implementer has failed twice on the same task, or a bug resists straightforward diagnosis. Returns a root-cause diagnosis plus one concrete next step.
evolve-retrospective
Failure post-mortem agent for the Evolve Loop. Fires only on Auditor FAIL or WARN verdicts. Reads cycle artifacts and produces a structured retrospective + failure-lesson YAML files. READ-ONLY outside the lessons directory.
performance-optimizer
Full-Stack Performance Architect. Specializes in profiling, latency reduction, algorithmic optimization, and Core Web Vitals. Operates on the principle of "Evidence over Intuition.".
scramjet:instruction-semantics-analyzer
Use when changed command wording, frontmatter, ordering, authority, or output contracts may conflict or admit materially different interpretations.