Borrowing it
Nothing to install: this file belongs to webhook-co/webhook. 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/webhook-co/webhook/main/.claude/skills/support-triage/SKILL.mdgit clone --depth 1 https://github.com/webhook-co/webhookWrote 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/webhook-co/webhook/support-triage)<a href="https://agentmods.dev/skills/webhook-co/webhook/support-triage"><img src="https://agentmods.dev/badge/skills/webhook-co/webhook/support-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/webhook-co/webhook/support-triage"><img src="https://agentmods.dev/badge/skills/webhook-co/webhook/support-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.00044 | $0.00421 |
| Opus 5.5 | $0.00018 | $0.00168 |
| Sonnet 5.5 | $0.00009 | $0.00084 |
| Haiku 4.5 | $0.00004 | $0.00042 |
Grade A, and why
support-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 1mo 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
Support triage
Turn a vague technical report into a precise, reproducible, routable finding. Technical triage only.
Triage flow
- Restate the problem in one line: which surface (CLI/API/web/MCP), which capability (receive / inspect / replay / deliver), and the observed vs expected behavior.
- Reproduce with the smallest case: endpoint setup, a sample (redacted) event, the exact command/request. Note environment and version.
- Localize using OpenTelemetry traces and logs — follow the event id through ingest → DO → delivery. Check dedup/idempotency, retry/backoff state, and signature verification.
- Classify: bug vs misuse vs expected behavior; severity (data-loss/security > delivery failure > cosmetic); and the owning area (engine, a surface, infra, docs).
- Write the finding: summary, repro steps, expected vs actual, evidence (trace/log refs), suspected cause, and a suggested owner. Add a regression-test idea for any real bug.
Handling data safely
- Redact PII/PHI before quoting payloads/logs in any report. Never paste secrets, tokens, or full bodies.
- Reference events by id, not by contents.
Guardrails
- Stay technical and public-safe: no customer identities, no pricing/billing internals, no business strategy in write-ups.
- If the issue looks like a security problem (authz bypass, SSRF, secret/PII leak), escalate to a security review rather than patching ad hoc.
Progressive disclosure
Keep deep-dive playbooks (delivery-failure decision tree, signature-mismatch checklist) in
references/.
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.
- 1mo ago First seen · 40 lines · 44 tokens per session scan A d3960509f810
support-triage is a skill published in the GitHub repository webhook-co/webhook (0 stars, last pushed 18d ago), licensed Apache-2.0. It adds 44 tokens to every session and 421 once invoked, about $0.0002 per session on Opus 5.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
triage
Diagnose and fix broken MCP servers in mcptoon — doctor, health, per-server probes, and the common failure playbook.
metagit-workspace-grep
Search on-disk file contents across managed workspace repos via ripgrep (or Python fallback). Use when hunting code strings, configs, or Terraform/Docker patterns — not for manifest metadata.
metagit-upstream-scan
Use when a coding agent encounters likely upstream blockers and must find related workspace repositories, files, and probable root causes.
metagit-upstream-triage
Triage cross-repository blockers by ranking likely upstream repositories and files with metagit search and hinting tools. Use when local fixes appear incomplete.
scan
A source-code scanner that checks a specified folder, or the workspace root by default, using an MCP scanning tool. Its results are heuristic signals, not a legal conclusion.
api-errors
McpError constructor, JsonRpcErrorCode reference, and error handling patterns for @cyanheads/mcp-ts-core. Use when looking up error codes, understanding where errors should be thrown vs. caught, or using ErrorHandler.tryCatch in services.