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 spencerpauly/skills-repo --skill triage-buggit clone --depth 1 https://github.com/spencerpauly/skills-repoWrote 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/spencerpauly/skills-repo/triage-bug)<a href="https://agentmods.dev/skills/spencerpauly/skills-repo/triage-bug"><img src="https://agentmods.dev/badge/skills/spencerpauly/skills-repo/triage-bug/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/spencerpauly/skills-repo/triage-bug"><img src="https://agentmods.dev/badge/skills/spencerpauly/skills-repo/triage-bug.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.00425 |
| Opus 5 | $0.00026 | $0.00212 |
| Sonnet 5 | $0.00011 | $0.00085 |
| Haiku 4.5 | $0.00005 | $0.00042 |
Grade A, and why
triage-bug 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.
What it actually says
Triage Bug
Convert a noisy bug report into a ticket someone can act on: one-line title, repro steps, severity, area.
When to use
- Support escalates a bug.
- A teammate dumps a Slack thread or screenshot.
- The user says "triage this" or "what's this bug".
Steps
- Re-read the report once, in full. Don't start writing yet.
- Restate the symptom in one sentence as a user would say it. No internal jargon.
- Pull out repro steps even if the original report doesn't separate them. Number them 1, 2, 3.
- Note the gap between expected and actual.
- Decide severity with this rubric:
- S1 — production down, data loss, or security issue.
- S2 — common path broken, no workaround.
- S3 — broken with workaround.
- S4 — cosmetic / rare path.
- Identify the area (one of: editor, billing, auth, api, infra, marketing).
Output format
## Title
<one line, present tense, no "bug:" prefix>
## Severity
S2
## Area
billing
## Repro
1. ...
2. ...
3. ...
## Expected vs actual
- Expected: ...
- Actual: ...
## Notes
- URLs, screenshots, affected user IDs.
Don't
- Don't open with "I think the issue is..." — the title goes first.
- Don't skip severity. Every ticket gets one, even if it's a guess.
- Don't paste raw stack traces into the title. Summarize.
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 · 60 lines · 53 tokens per session scan A 2222051a22d2
triage-bug is a skill published in the GitHub repository spencerpauly/skills-repo (25 stars, last pushed 2mo ago), licensed MIT. It adds 53 tokens to every session and 425 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
systemic-issue-triage
Trigger: new issue, bug report, triage, backlog, issue flood, community report, root cause, dead-end, blocked user. Attack issues by root class, never one-by-one; fixes must shrink the system, not grow it.
triage-issue
Intelligently triage bug reports and error messages by searching for duplicates in Jira and offering to create new issues or add comments to existing ones. When an agent needs to: (1) Triage a bug report or error message, (2) Check if an issue is a duplicate, (3) Find similar past issues, (4) Create a new bug ticket…
bug-triage
Read all open bugs in production/qa/bugs/, re-evaluate priority vs. severity, assign to sprints, surface systemic trends, and produce a triage report. Run at sprint start or when the bug count grows enough to need re-prioritization.
browse-flows
Browse Power Automate environments and flows interactively. Use when the user wants to browse, list, or explore their flows and environments.
operating-cadence
Designs the rhythm an organization runs on — which reviews happen weekly, monthly and quarterly, what each one decides, who owns the numbers presented, and how a signal at the front line reaches the people who can act on it. Use this to set up a management operating system, fix a meeting calendar that produces no…
status
Display current FIRE project status and validate integrity of intents, work items, and runs.