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 carofi-auto/agent-skills --skill triagegit clone --depth 1 https://github.com/carofi-auto/agent-skillsWrote 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/carofi-auto/agent-skills/triage)<a href="https://agentmods.dev/skills/carofi-auto/agent-skills/triage"><img src="https://agentmods.dev/badge/skills/carofi-auto/agent-skills/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/carofi-auto/agent-skills/triage"><img src="https://agentmods.dev/badge/skills/carofi-auto/agent-skills/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.00053 | $0.02121 |
| Opus 5 | $0.00026 | $0.01060 |
| Sonnet 5 | $0.00011 | $0.00424 |
| Haiku 4.5 | $0.00005 | $0.00212 |
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 9d 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 — 213 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Triage — Code Diagnosis
THE IRON LAW: NO FIXES WITHOUT ROOT CAUSE CONFIRMED FIRST. Symptom fixes are failure. Root cause first. Always.
Given any issue description (ticket, freeform, paste), trace to root cause. Output diagnosis block. Wait for confirmation. Fix only after user says go.
Scope
In: correctness bugs, unexpected behavior, test failures, crashes, integration issues, latency regression, resource exhaustion (memory leak, connection pool, GC pressure) Out: performance optimization requests, security audits, architecture reviews, feature requests, infra/DevOps issues
Invocation
Paste or describe the issue after /triage. Claude classifies, investigates, diagnoses, waits for confirmation, then fixes.
Phase 1 — Classify + Reproduce
Identify issue type AND confirm reproducibility before touching any code.
Reproduce first:
- Can you trigger it reliably? What are the exact steps?
- Does it happen every time, or intermittently?
- If not reproducible → gather more data, do not guess, do not fix
| Type | Signal |
|---|---|
| Stack trace / crash | Error message, exception, unhandled rejection |
| Unexpected behavior | "X should do Y but does Z" |
| Test failure | Failing assertion, expected vs actual mismatch |
| Integration issue | Two systems not communicating, missing data at boundary |
| Latency / resource bug | Regression in response time, memory growth, connection exhaustion |
| Vague / mixed | Extract the symptom, treat as unexpected behavior |
Test failure sub-type:
- Regression — was passing, now failing → check recent changes first
- Flaky — intermittent → suspect concurrency, timing, or state leakage
- New — never passed → trace logic against spec
Environment flag:
- Is this only in staging / prod / one region? If yes: check config, secrets, feature flags, data differences before touching code.
Cascading failures:
- Find the first failure, not the loudest symptom. Trace from the failing dependency, not the visible error.
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.
- 9d ago First seen · 213 lines · 53 tokens per session scan A f32bd96a4a1e
triage is a skill published in the GitHub repository carofi-auto/agent-skills (5 stars, last pushed 2mo ago), licensed MIT. It adds 53 tokens to every session and 2,121 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-31.
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…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.