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 agentmods add commands/arrrrny/zuraffa/speckit.bug.issuegit 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/commands/arrrrny/zuraffa/speckit.bug.issue)<a href="https://agentmods.dev/commands/arrrrny/zuraffa/speckit.bug.issue"><img src="https://agentmods.dev/badge/commands/arrrrny/zuraffa/speckit.bug.issue.svg" alt="Measured on agentmods" 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 | $0.00021 | $0.01508 |
| Opus 5 | $0.00010 | $0.00754 |
| Sonnet 5 | $0.00004 | $0.00302 |
| Haiku 4.5 | $0.00002 | $0.00151 |
Grade A, and why
speckit.bug.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 5d 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Report Bug (Create Issue)
Turn a local bug assessment into a tracked GitHub issue. This command reads .specify/bugs/<slug>/assessment.md (produced by __SPECKIT_COMMAND_BUG_ASSESS__) and creates a GitHub issue via the gh CLI, then records the issue number and URL in BUG_DIR/issue.md. If gh or a GitHub remote is unavailable, it writes a ready-to-paste draft instead so no work is lost.
User Input
$ARGUMENTS
Accept any of:
slug=<bug-slug>or--slug <bug-slug>or a bare slug-like token.- A path that contains the slug (e.g.
.specify/bugs/login-timeout/). - Nothing — fall back to context (see Slug Resolution).
Slug Resolution
Resolve BUG_SLUG in this order, stopping at the first match:
- Explicit user input — a slug passed in
$ARGUMENTS(any of the forms above). - Conversation context — if the current session has just run
__SPECKIT_COMMAND_BUG_ASSESS__, the slug it reported is the working slug. Reuse it without re-prompting. - Single candidate on disk — list
.specify/bugs/*/assessment.md. If exactly one matchingassessment.mdis found, use the slug from its parent directory. - Disambiguate:
- Interactive mode: ask the user which bug to report and list the candidates.
- Automated mode: stop with an error listing the candidates. Do not guess.
Once resolved, set BUG_SLUG and BUG_DIR = .specify/bugs/<BUG_SLUG>.
Prerequisites
BUG_DIR/assessment.mdMUST exist. If it does not, stop and instruct the user to run__SPECKIT_COMMAND_BUG_ASSESS__first.- Read
BUG_DIR/assessment.mdin full. Treat its Symptom, Reproduction, Suspected Code Paths, Root Cause Hypothesis, Severity, and Source fields as the basis for the issue. - Detect GitHub context:
- Run
git rev-parse --is-inside-work-tree 2>/dev/nullto confirm a repository. - Run
git config --get remote.origin.urlto read the remote. Parseownerandrepo(HTTPShttps://github.com/<owner>/<repo>.gitor SSH[email protected]:<owner>/<repo>.git). Only proceed with issue creation when the remote points togithub.com.
- Run
- Check for
ghwithcommand -v gh >/dev/null 2>&1. If absent, or the remote is not GitHub, or the user is not authenticated (gh auth statusfails), skip live creation and write a draft (see Graceful Degradation).
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.
- 5d ago First seen · 98 lines · 21 tokens per session scan A 91d86ff095e4
speckit.bug.issue is a command published in the GitHub repository arrrrny/zuraffa (5 stars, last pushed yesterday), licensed MIT. It adds 21 tokens to every session and 1,508 once invoked, about $0.0001 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 commands, from other repositories
building-flutter-apps-skill-ac1294fc
Flutter Riverpod app architecture and Windows installer delivery. Use before changing a Riverpod Flutter app/package or its Windows desktop packaging/update pipeline; skip non-Riverpod stacks and pure-Dart work.
Generate Implementation Plan
Create intelligent, dependency-aware implementation plan with sprint planning and team allocation.
Analyze Feature Dependencies
Map feature dependencies and suggest optimal implementation order.
Analyze PRD
Validate and analyze PRD with quality scoring, show customizations.
Auto-Generate PRD from All Project Files
Automatically discover and consolidate all markdown files in project into comprehensive PRD.
Refine PRD
Interactively improve PRD quality through AI-guided analysis and refinement.