Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add ashlrai/ashlr-plugin/plugin install ashlrWrote 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/ashlrai/ashlr-plugin/ashlr-report-crash)<a href="https://agentmods.dev/commands/ashlrai/ashlr-plugin/ashlr-report-crash"><img src="https://agentmods.dev/badge/commands/ashlrai/ashlr-plugin/ashlr-report-crash.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.00045 | $0.00529 |
| Opus 5 | $0.00023 | $0.00264 |
| Sonnet 5 | $0.00009 | $0.00106 |
| Haiku 4.5 | $0.00005 | $0.00053 |
Grade A, and why
ashlr-report-crash 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.
What it actually says
Run the report-crash script and help the user review what will leave their machine before it uploads.
Steps:
-
Run this command via Bash:
bun run ${CLAUDE_PLUGIN_ROOT}/scripts/report-crash.ts $ARGUMENTSIf
$CLAUDE_PLUGIN_ROOTis unset, resolve the plugin root by walking up from a known ashlr path until.claude-plugin/plugin.jsonis found (same resolution as/ashlr-doctor). -
Print the script's stdout/stderr verbatim. The script owns the preview, the confirm prompt, and the upload — do not paraphrase. It exits 0 on success, 1 if no crashes found, 2 if the user declined, 3 on network error.
-
If the user is unsure whether to upload, recommend
--dry-runfirst: it shows exactly the JSON that would leave the machine without sending anything.
Flags (forwarded via $ARGUMENTS):
| Flag | Purpose |
|---|---|
--dump <path> |
Upload a specific ~/.ashlr/crashes/YYYY-MM-DD.jsonl file instead of the most recent record |
--all |
Upload every record from the last 7 days (default: 1 most-recent) |
--dry-run |
Preview only — print what would be sent, do not upload |
--stdout |
Print the redacted record(s) to stdout so the user can paste into a GitHub issue |
--yes |
Skip the "confirm before upload" prompt |
--endpoint <url> |
Override the upload endpoint (defaults to $ASHLR_CRASH_UPLOAD_URL or production) |
Privacy posture: dumps are already redacted at write time by servers/_crash-dump.ts (Authorization headers, sk-*/gh*_* tokens, 40-char hex, key/value pairs named token/apiKey/secret/password/cookie). The upload path does not add anything beyond what's already on disk plus pluginVersion and process.platform. No cwd, no paths beyond the crash args that were already in the tool call at crash time, no stdin/stdout of any command.
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 · 34 lines · 45 tokens per session scan A 9945e8a75212
ashlr-report-crash is a command published in the GitHub repository ashlrai/ashlr-plugin (3 stars, last pushed yesterday), licensed MIT. It adds 45 tokens to every session and 529 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-31.
Other commands, from other repositories
rescue
Hand a stuck or open-ended problem to Codex for an independent investigation or rescue pass.
ccc-debug-session
Start a structured debug session with hypothesis tracking and resolution documentation.
perf
Structured performance investigation with baselines, profiling, and evidence-backed decisions.
scan
A codebase onboarding briefing that examines a new project's files, tools, main entry points, and marked technical debt.
bug-fix
Streamlines bug fixing by creating a GitHub issue first, then a feature branch for implementing and thoroughly testing the solution before merging.
fix
Systematic, step-by-step debugging — no rushing. Reproduce the bug, trace logs + DB step by step, judge the root cause, write a failing test, then fix minimally.