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.prgit 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.pr)<a href="https://agentmods.dev/commands/arrrrny/zuraffa/speckit.bug.pr"><img src="https://agentmods.dev/badge/commands/arrrrny/zuraffa/speckit.bug.pr.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.1 | $0.00014 | $0.01448 |
| Opus 5 | $0.00007 | $0.00724 |
| Sonnet 5 | $0.00003 | $0.00290 |
| Haiku 4.5 | $0.00001 | $0.00145 |
Grade A, and why
speckit.bug.pr 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- speckit.chore.pr — 89% identical, 61 lines differ
How it starts
The opening of the file, as written. The whole thing — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Open Fix Pull Request
Open a GitHub pull request for the fix recorded by __SPECKIT_COMMAND_BUG_FIX__. This command reads .specify/bugs/<slug>/fix.md (and issue.md if the bug was reported) and creates a PR via the gh CLI from the current branch, linking the issue. If gh or a GitHub remote is unavailable, it writes a ready-to-paste PR draft instead.
This command is the natural follow-up when
bug.fixwas run with--branch/--worktree: the current branch is the fix branch (e.g.fix/<slug>) and the PR opens from it.
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_FIX__(orbug.issue), the slug it reported is the working slug. Reuse it without re-prompting. - Single candidate on disk — list
.specify/bugs/*/fix.md. If exactly one bug has afix.md, use it. - Disambiguate:
- Interactive mode: ask the user which bug to open a PR for 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/fix.mdMUST exist. If it does not, stop and instruct the user to run__SPECKIT_COMMAND_BUG_FIX__first.- Confirm the current branch is the fix branch (created by
bug.fix --branch, or whatever branch holds the change). If the working tree is onmain/masterwith uncommitted changes, warn the user and ask which branch to open the PR from before continuing. - Detect GitHub context (same as
bug.issue):git rev-parse --is-inside-work-treeandgit config --get remote.origin.urlto parseowner/repo; only proceed live when the remote isgithub.com.command -v ghandgh auth statusto confirm the CLI and auth.- If
gh/GitHub remote/auth is unavailable, 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 · 95 lines · 14 tokens per session scan A 7536a6ca1d35
speckit.bug.pr is a command published in the GitHub repository arrrrny/zuraffa (5 stars, last pushed today), licensed MIT. It adds 14 tokens to every session and 1,448 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.