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 skills/code-payments/code-android-app/triagenpx skills add code-payments/code-android-app --skill triagegit clone --depth 1 https://github.com/code-payments/code-android-appWhat 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 | $0.00054 | $0.01826 |
| Opus 5 | $0.00027 | $0.00913 |
| Sonnet 5 | $0.00011 | $0.00365 |
| Haiku 4.5 | $0.00005 | $0.00183 |
Grade A, and why
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 yesterday.
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 — 205 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. Follow the steps below exactly.
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).
Source .env from the repo root if the variable is not already set.
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)
Step 3 — Map stack frames to source
Android stack frames use Java/Kotlin package-qualified class names (e.g.
com.flipcash.features.cash.CashViewModel). To locate the source file:
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.
- yesterday 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 2d ago), licensed MIT. It adds 54 tokens to every session and 1,826 once invoked, about $0.0003 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…