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/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)<a href="https://agentmods.dev/skills/stbenjam/skillsaw/skillsaw-issue"><img src="https://agentmods.dev/badge/skills/stbenjam/skillsaw/skillsaw-issue/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"><img src="https://agentmods.dev/badge/skills/stbenjam/skillsaw/skillsaw-issue.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.00052 | $0.00673 |
| Opus 5 | $0.00026 | $0.00336 |
| Sonnet 5 | $0.00010 | $0.00135 |
| Haiku 4.5 | $0.00005 | $0.00067 |
Grade A, and why
skillsaw-issue 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 11d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
skillsaw Issue
Use this skill when skillsaw itself needs a GitHub issue: a false positive, a missed violation, a crash, incorrect autofix, an edge case in rule detection, or a request for enhancement (RFE). Do not use it to report a problem in the repository being linted unless that problem demonstrates incorrect skillsaw behavior or a useful feature gap.
Gather safe evidence first
Collect the minimum evidence needed to explain the issue without sending anything externally:
- skillsaw version and the exact command
- affected rule ID, file type, and relevant configuration
- expected behavior and actual behavior for a bug
- user goal and proposed outcome for an RFE
- a minimal reproducer or a short sanitized excerpt
Never copy credentials, private repository content, or complete diagnostic output into an issue draft. Prefer a minimal synthetic reproducer.
Require separate permission for each external action
Ask the user two explicit questions before taking either action:
- "May I run
skillsaw feedbackto create a local diagnostic ZIP?" - "May I open an issue in
stbenjam/skillsaw?"
Do not run skillsaw feedback without permission for the first action. Do
not create a GitHub issue without permission for the second action. Permission
for one action does not authorize the other. If permission is absent, present
a sanitized draft and ask for the missing approval.
Create a feedback bundle only when approved
Run skillsaw feedback <repository-path> with a concise --message that
describes the observed behavior. The command creates a local ZIP; it does not
submit anything. Do not add --include unless the user explicitly identifies
the file to share.
Review the ZIP before sharing it. skillsaw does not scan file contents for
secrets: anything --include or --config names is copied in verbatim, so
read those files yourself and remove or replace anything sensitive. Keep the
bundle local if the user does not also approve opening an issue.
Open an issue only when approved
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.
- 11d ago First seen · 71 lines · 52 tokens per session scan A bbd681d7904b
skillsaw-issue is a skill published in the GitHub repository stbenjam/skillsaw (66 stars, last pushed 2d ago), licensed Apache-2.0. It adds 52 tokens to every session and 673 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
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.