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 arrrrny/zuraffa --skill speckit-gh-triage-triagegit clone --depth 1 https://github.com/arrrrny/zuraffaWrote 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/arrrrny/zuraffa/speckit-gh-triage-triage)<a href="https://agentmods.dev/skills/arrrrny/zuraffa/speckit-gh-triage-triage"><img src="https://agentmods.dev/badge/skills/arrrrny/zuraffa/speckit-gh-triage-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/arrrrny/zuraffa/speckit-gh-triage-triage"><img src="https://agentmods.dev/badge/skills/arrrrny/zuraffa/speckit-gh-triage-triage.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 217 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00086 | $0.03469 |
| Opus 5 | $0.00043 | $0.01734 |
| Sonnet 5 | $0.00017 | $0.00694 |
| Haiku 4.5 | $0.00009 | $0.00347 |
Grade A, and why
speckit-gh-triage-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 7d 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 — 219 lines — stays where its author put it; the contents beside it link to each section on GitHub.
GitHub Triage
Batch-triage the open GitHub issues for a repository. For every issue this command: (1) fetches it, (2) classifies it as bug, feature, or chore, (3) labels it with the correct triage labels read directly from config (on by default), and (4) delegates to the correct extension command to save it in the right place:
- bug → delegate to the bug extension:
/speckit-bug-fetchsaves under.specify/bugs/<slug>/, then/speckit-bug-assessfor triage. Do NOT call/speckit-specifyfor bugs. - chore → delegate to the chore extension:
/speckit-chore-fetchsaves under.specify/chores/<slug>/, then/speckit-chore-assessfor scoping. Do NOT call/speckit-specifyfor chores. - feature → the core
/speckit-specifycommand for new features, which saves underspecs/<n>-<slug>/.
A chore is maintenance work that is neither a bug (something broken) nor a
feature (new user-facing capability): refactors, dependency bumps, asset/branding
swaps, config cleanups, tooling changes. Chores stay in the Spec Kit ecosystem
and are constitution-aware (the chore extension consults the project
constitution when scoping them).
This extension requires the bug extension (fetch, assess, issue, fix, pr,
test), the chore extension (fetch, assess, issue, implement, pr), and the core
speckit.specify command. The deterministic fetch / classify / label phases are
handled by a bundled engine so they are fast, repeatable, and testable; the
routing phase is performed by you, following the steps below.
User Input
$ARGUMENTS
Accept any of:
--repo <owner>/<repo>— triage a specific repo (elserepo:from config, else the current git remote).--limit <N>— triage at mostNopen issues (0 / omitted = all).--issue <N>— triage a single issue number instead of the open list.--dry-run/--no-label— classify and report the labels that would be applied, but do not change any issue (safe preview).- A bare issue number or
owner/repo#nis treated as--issue <n>/--repo.
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.
- 7d ago Changed · +218 lines · +86 tokens per session 665f8d11a36a
- 9d ago Changed 4f844a51e928
- 12d ago First seen · 1 lines · 0 tokens per session scan A 241d7579565f
speckit-gh-triage-triage is a skill published in the GitHub repository arrrrny/zuraffa (5 stars, last pushed yesterday), licensed MIT. It adds 86 tokens to every session and 3,469 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
quality
Evaluates whether a GitHub issue is spam, empty, needs more information, or is OK to proceed.
follow-up-after-call
Use after a completed customer, prospect, partner, or important internal sales call, discovery session, demo, or conversation, including when the user supplies or uploads a transcript, notes, recording summary, or other grounded evidence. Advise on, assess, qualify, recap, and produce seller-ready follow-up actions…
persona-event-coordinator
Plan and manage events — scheduling, invitations, and logistics.
persona-project-manager
Coordinate projects — track tasks, schedule meetings, and share docs.
persona-team-lead
Lead a team — run standups, coordinate tasks, and communicate.
recipe-plan-weekly-schedule
Review your Google Calendar week, identify gaps, and add events to fill them.