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 hanamizuki/solopreneur --skill asc-crash-triagegit clone --depth 1 https://github.com/hanamizuki/solopreneurWrote 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/hanamizuki/solopreneur/asc-crash-triage)<a href="https://agentmods.dev/skills/hanamizuki/solopreneur/asc-crash-triage"><img src="https://agentmods.dev/badge/skills/hanamizuki/solopreneur/asc-crash-triage/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/hanamizuki/solopreneur/asc-crash-triage"><img src="https://agentmods.dev/badge/skills/hanamizuki/solopreneur/asc-crash-triage.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.00060 | $0.00832 |
| Opus 5.5 | $0.00024 | $0.00333 |
| Sonnet 5.5 | $0.00012 | $0.00166 |
| Haiku 4.5 | $0.00006 | $0.00083 |
Grade A, and why
asc-crash-triage 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 20d 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.
This is a copy
100% identical to asc-crash-triage — 14 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
asc crash triage
Use this skill to fetch, analyze, and summarize TestFlight crash reports, beta feedback, and performance diagnostics.
Workflow
- Resolve the app ID if not provided (use
asc apps list). - Fetch data with the appropriate command.
- Parse JSON output and present a human-readable summary.
TestFlight crash reports
List recent crashes (newest first):
asc testflight crashes list --app "APP_ID" --sort -createdDate --limit 10- Filter by build:
asc testflight crashes list --app "APP_ID" --build "BUILD_ID" --sort -createdDate --limit 10 - Filter by device/OS:
asc testflight crashes list --app "APP_ID" --device-model "iPhone16,2" --os-version "18.0" - All crashes:
asc testflight crashes list --app "APP_ID" --paginate - Table view:
asc testflight crashes list --app "APP_ID" --sort -createdDate --limit 10 --output table
TestFlight beta feedback
List recent feedback (newest first):
asc testflight feedback list --app "APP_ID" --sort -createdDate --limit 10- With screenshots:
asc testflight feedback list --app "APP_ID" --sort -createdDate --limit 10 --include-screenshots - Filter by build:
asc testflight feedback list --app "APP_ID" --build "BUILD_ID" --sort -createdDate - All feedback:
asc testflight feedback list --app "APP_ID" --paginate
Performance diagnostics (hangs, disk writes, launches)
Requires a build ID. Resolve via asc builds info --app "APP_ID" --latest --platform IOS or asc builds list --app "APP_ID" --sort -uploadedDate --limit 5.
- List diagnostic signatures:
asc performance diagnostics list --build "BUILD_ID" - Filter by type:
asc performance diagnostics list --build "BUILD_ID" --diagnostic-type "HANGS"- Types:
HANGS,DISK_WRITES,LAUNCHES
- Types:
- View logs for a signature:
asc performance diagnostics view --id "SIGNATURE_ID" - Download all metrics:
asc performance download --build "BUILD_ID" --output ./metrics.json
Resolving IDs
- App ID from name:
asc apps list --name "AppName"orasc apps list --bundle-id "com.example.app" - Latest build ID:
asc builds info --app "APP_ID" --latest --platform IOS - Recent builds:
asc builds list --app "APP_ID" --sort -uploadedDate --limit 5 - Set default:
export ASC_APP_ID="APP_ID"
What ships with it
1 file 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.
- 20d ago First seen · 70 lines · 60 tokens per session scan A 3553b13b4c07
asc-crash-triage is a skill published in the GitHub repository hanamizuki/solopreneur (154 stars, last pushed 4d ago), licensed MIT. It adds 60 tokens to every session and 832 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to asc-crash-triage, differing in 14 lines, and is treated as a copy.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
deck-retro
Run a fully local agent-deck retrospective over the user's own transcripts, Recall index and logs. Use when a user wants to find recurring failures or take their own finding from investigation through synthetic reproduction, a user-filed issue, a test-first fix and contributor PR handoff. Also use for weekly usage…