Borrowing it
Nothing to install: this file belongs to code-payments/code-android-app. 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/code-payments/code-android-app/code/cash/.claude/skills/triage/SKILL.mdgit clone --depth 1 https://github.com/code-payments/code-android-appWrote 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/code-payments/code-android-app/triage)<a href="https://agentmods.dev/skills/code-payments/code-android-app/triage"><img src="https://agentmods.dev/badge/skills/code-payments/code-android-app/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/code-payments/code-android-app/triage"><img src="https://agentmods.dev/badge/skills/code-payments/code-android-app/triage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00054 | $0.01970 |
| Opus 5.5 | $0.00022 | $0.00788 |
| Sonnet 5.5 | $0.00011 | $0.00394 |
| Haiku 4.5 | $0.00005 | $0.00197 |
Grade A, and why
triage scanned grade A with 1 finding 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 27d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s -H "Authorization: token $BUGSNAG_TOKEN" "<event_url>" How it starts
The opening of the file, as written. The whole thing — 217 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Triage: daily Bugsnag issue investigation
You are a senior Android engineer performing daily Bugsnag triage for the Flipcash Android app.
Done when .claude/plans/triage-<error_id>.md follows the template and names a
root cause backed by .kt:NN evidence, or states your confidence and what
evidence is missing. The steps below are the usual path; skip any the evidence
makes unnecessary.
Step 1 — Fetch the issue
If the user provided a Bugsnag URL or error ID, pass it to the helper script:
# Specific issue by URL
bash .claude/skills/triage/scripts/bugsnag-top.sh --url "https://app.bugsnag.com/org/project/errors/abc123"
# Specific issue by error ID
bash .claude/skills/triage/scripts/bugsnag-top.sh --error-id abc123
Otherwise, fetch the top open issue automatically:
bash .claude/skills/triage/scripts/bugsnag-top.sh
The script emits a single JSON object with:
| Field | Description |
|---|---|
error_id |
Bugsnag error group ID |
error_url |
Deep link into the Bugsnag dashboard |
event_url |
REST API URL for the latest event |
title |
Error class + message |
severity |
error / warning / info |
events |
Total occurrences |
users |
Unique affected users |
first_seen |
ISO-8601 timestamp |
release |
app_version from the latest event |
If the script exits non-zero, stop and report the error to the user.
Step 2 — Pull event detail
Fetch event_url (include header Authorization: token $BUGSNAG_TOKEN).
The token lives in .env or .env.local at the repo root, as the script reads
it; load both in the same shell as the request:
set -a; [ -f .env ] && . ./.env; [ -f .env.local ] && . ./.env.local; set +a
curl -s -H "Authorization: token $BUGSNAG_TOKEN" "<event_url>"
Parse the response using the event shape documented in
.claude/skills/triage/references/event-shape.md.
Extract four evidence sources:
- Stack trace —
exceptions[0].stacktrace(frames withfile,method,lineNumber,inProject) - Exception info —
exceptions[0].errorClass+exceptions[0].message - App logs —
metaData["App Logs"]["app_log"](single string, last ~64 KB of log output) - Breadcrumbs —
breadcrumbs[](timestamped UI / state / network events)
What ships with it
3 files 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.
- 27d ago Changed · +6 lines 22704d095155
- 1mo ago Changed · +6 lines 2846c5a7d22b
- 2mo ago First seen · 205 lines · 54 tokens per session scan A bf54e178c9c0
triage is a skill published in the GitHub repository code-payments/code-android-app (23 stars, last pushed today), licensed MIT. It adds 54 tokens to every session and 1,970 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
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.
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…
cwv-optimizer
Diagnose and fix Core Web Vitals issues on AEM Edge Delivery Services pages. Goes deeper than generic CWV advice by understanding EDS-specific performance patterns including the 100KB LCP budget, E-L-D loading phases, block rendering behavior, and third-party script impact. Produces specific fixes for LCP, CLS, and…
incident-response-incident-response
Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.
ci-fixer
CI failures - read error, minimal fix, verify.
diagnosing-missing-recordings
Diagnoses why a session recording is missing or was not captured. Use when a user asks why a session has no replay, why recordings aren't appearing, or wants to troubleshoot session replay capture issues for a specific session ID or across their project. Covers SDK diagnostic signals, project settings, sampling…