Borrowing it
Nothing to install: this file belongs to stbenjam/skillsaw. 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/stbenjam/skillsaw/main/.agents/skills/skillsaw-issue-triage/SKILL.mdgit clone --depth 1 https://github.com/stbenjam/skillsawWrote 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/stbenjam/skillsaw/skillsaw-issue-triage)<a href="https://agentmods.dev/skills/stbenjam/skillsaw/skillsaw-issue-triage"><img src="https://agentmods.dev/badge/skills/stbenjam/skillsaw/skillsaw-issue-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/stbenjam/skillsaw/skillsaw-issue-triage"><img src="https://agentmods.dev/badge/skills/stbenjam/skillsaw/skillsaw-issue-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.00068 | $0.01345 |
| Opus 5 | $0.00034 | $0.00673 |
| Sonnet 5 | $0.00014 | $0.00269 |
| Haiku 4.5 | $0.00007 | $0.00135 |
Grade A, and why
skillsaw-issue-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 12d 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
skillsaw Issue Triage
Triage a single open issue on the skillsaw linter. Check what kind of
issue it is, check whether its claims hold up against the actual code, fill in
the details it is missing, review the evidence, and leave one triage
comment. This skill triages issues — never fix them here (that job belongs to skillsaw-issue-solver).
Read the detailed evaluation checklist for each classification in references/,
and read only the checklist for the class the issue falls into (progressive disclosure).
Keep this file lean and pull the checklist in on demand.
Step 1 — Read the Issue
Run this for the issue number you were given:
gh issue view <number> --json number,title,body,labels,author,comments,createdAt
Read the title, body, and every comment before judging anything. Note the skillsaw version the reporter names (or none), and check any config, command, or file content they pasted.
Step 2 — Classify
Set exactly one primary class. When an issue spans two, pick the one that determines the next action and note the secondary in the comment.
| Class | The issue is… | Evaluation checklist |
|---|---|---|
bug |
A claim that skillsaw behaves incorrectly — wrong violation, crash, false positive/negative, bad autofix | references/bug-evaluation.md |
feature |
A request for new behavior — a new rule, flag, config option, output format, or tool/format support | references/feature-evaluation.md |
documentation |
Docs are missing, wrong, or unclear (README, skillsaw.org, rule docs) — code behavior is not disputed | references/other-evaluation.md |
question |
A usage/support question, not a defect or request | references/other-evaluation.md |
other |
Duplicate, invalid, spam, out-of-scope, or needs-more-info | references/other-evaluation.md |
What ships with it
4 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.
- 12d ago First seen · 103 lines · 68 tokens per session scan A 2dd105f15b73
skillsaw-issue-triage is a skill published in the GitHub repository stbenjam/skillsaw (66 stars, last pushed 3d ago), licensed Apache-2.0. It adds 68 tokens to every session and 1,345 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
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
llxprt-issue-workflow
Use this skill when asked to address, fix, or work on a GitHub issue in the llxprt-code repository. Covers the complete issue lifecycle - branch setup, gh CLI usage, test-first planning, subagent delegation and review loops, the full verification cycle (including the stepfun-37 smoke test), open code review (ocr), PR…
cyrus-setup-repository
Add one or more Git repositories to Cyrus configuration so it can process issues from those repos.
github-sync
Bidirectional synchronization of epics and tasks with GitHub issues, labels, and relationships.
github-notification-triage
Triage GitHub notifications and issue/PR queues.