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 lttr/claude-marketplace --skill triagegit clone --depth 1 https://github.com/lttr/claude-marketplaceWrote 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/lttr/claude-marketplace/triage)<a href="https://agentmods.dev/skills/lttr/claude-marketplace/triage"><img src="https://agentmods.dev/badge/skills/lttr/claude-marketplace/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/lttr/claude-marketplace/triage"><img src="https://agentmods.dev/badge/skills/lttr/claude-marketplace/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.00078 | $0.01557 |
| Opus 5 | $0.00039 | $0.00779 |
| Sonnet 5 | $0.00016 | $0.00311 |
| Haiku 4.5 | $0.00008 | $0.00156 |
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 6d 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 — 195 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Triage
Analyze requirements for completeness. Explore code + docs, surface gaps, ask clarifying questions, write a report.
Tracker-agnostic and storage-agnostic: fetching a ticket and choosing where the report lands are both pluggable (see references/sources.md).
Arguments
$ARGUMENTS is a space-separated string. Parse optional flags first, then treat the remainder as the input.
| Flag | Meaning |
|---|---|
--ticket <id> |
Ticket / work-item id (label + fetch hint). |
--name <title> |
Override inferred report title. |
--out <path> |
Write report to this path; skip the save prompt. |
--print |
Print report to stdout; skip the save prompt. |
Wrappers may pre-pin any of these — user-passed flags WIN.
Input Detection
After flags are stripped, the remainder selects the requirement source:
| Form | Source |
|---|---|
| empty | prompt user to paste / describe |
path ending .md |
local markdown spec file |
bare id (12345, PROJ-42) |
tracker ticket → see below |
| URL pointing at an issue/item | tracker ticket → see below |
| anything else | treat as pasted text |
Ambiguous → ask. Do NOT guess.
Workflow
1. Resolve input
empty
Prompt: "Paste requirements / spec text, or give a ticket id, URL, or .md path."
.md path
Read file. Use content as input. Title from H1 or filename.
pasted text
Use as-is. Derive title from first line / sentence.
tracker ticket
Read references/sources.md and use the first available fetch path. Never invent a CLI or an API call — if nothing is available, ask the user to paste the ticket text.
Normalize whatever comes back to: title, description, acceptance criteria, state, type, assignee, area/labels, linked items. HTML descriptions → readable text.
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.
- 6d ago Changed · +1 lines 34f22788a1bc
- 11d ago First seen · 194 lines · 78 tokens per session scan A a6a31ed2af1a
triage is a skill published in the GitHub repository lttr/claude-marketplace (2 stars, last pushed yesterday), licensed MIT. It adds 78 tokens to every session and 1,557 once invoked, about $0.0004 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
stream-chain
Stream-JSON chaining for multi-agent pipelines, data transformation, and sequential workflows.
hook-factory
Generate production-ready Claude Code hooks with interactive Q&A, automated installation, and enhanced validation. Supports 10 templates across 7 event types for comprehensive workflow automation.
html-ppt-hermes-cyber-terminal
OpenDesign + BYOK: choosing and wiring your own model, hands-on — cost, quality, and the routing decision. Built as a decision-grade AI literacy deck for engineers, IT, applied-AI teams.
r3f-best-practices
React Three Fiber (R3F) and Poimandres ecosystem best practices. Use when writing, reviewing, or optimizing R3F code. Triggers on tasks involving @react-three/fiber, @react-three/drei, zustand, @react-three/postprocessing, @react-three/rapier, or leva.
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…
development
An index of programming guidance for Python, Go, Rust, TypeScript, Java, C++, and shell scripting.