agentmods.dev

speckit-bug-issue

speckit-bug-issue is a skill for Claude Code from arrrrny/zuraffa. It costs 29 tokens per session (1,538 once invoked), scanned A, original, MIT.

A workflow for turning a bug assessment into a tracked GitHub issue. GitHub issues are shared records used to discuss and follow work in a repository.

In plain words
What is it for?
Use it to resolve a bug slug, create the issue with the gh command-line tool, and save the issue number and link locally.
Why use it?
It keeps an assessed bug from remaining only in local notes, while preserving a draft if GitHub tools are unavailable.

Skill for Claude Code

Written for Claude Code: $ARGUMENTS substitution. Also seen: installed under .agents/ (shared by several agents).

not rated 5repo changed 3d ago A scan 29 tokens original MIT

Good fit Use it to resolve a bug slug, create the issue with the gh command-line tool, and save the issue number and link locally.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/arrrrny/zuraffa/speckit-bug-issue
View source ↗ arrrrny/zuraffa zuraffa.com
Install

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.

Any agent
npx skills add arrrrny/zuraffa --skill speckit-bug-issue
Clone the repo
git clone --depth 1 https://github.com/arrrrny/zuraffa

Made for: Claude Code.

Wrote 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.

agentmods badge for speckit-bug-issue

README.md
[![agentmods](https://agentmods.dev/badge/skills/arrrrny/zuraffa/speckit-bug-issue/github.svg)](https://agentmods.dev/skills/arrrrny/zuraffa/speckit-bug-issue)
Your own site
<a href="https://agentmods.dev/skills/arrrrny/zuraffa/speckit-bug-issue"><img src="https://agentmods.dev/badge/skills/arrrrny/zuraffa/speckit-bug-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.

agentmods 80×15 button for speckit-bug-issue

Your own site · 80×15
<a href="https://agentmods.dev/skills/arrrrny/zuraffa/speckit-bug-issue"><img src="https://agentmods.dev/badge/skills/arrrrny/zuraffa/speckit-bug-issue.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 29 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,538 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00029 $0.01538
Opus 5 $0.00015 $0.00769
Sonnet 5 $0.00006 $0.00308
Haiku 4.5 $0.00003 $0.00154

Measured 3d ago against content hash ee8ff4c8d3a4, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

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 3d 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.

.agents/skills/speckit-bug-issue/SKILL.md · 102 lines

How it starts

The opening of the file, as written. The whole thing — 102 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-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:

  1. Explicit user input — a slug passed in $ARGUMENTS (any of the forms above).
  2. Conversation context — if the current session has just run /speckit-bug-assess, the slug it reported is the working slug. Reuse it without re-prompting.
  3. Single candidate on disk — list .specify/bugs/*/assessment.md. If exactly one matching assessment.md is found, use the slug from its parent directory.
  4. 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.md MUST exist. If it does not, stop and instruct the user to run /speckit-bug-assess first.
  • Read BUG_DIR/assessment.md in 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/null to confirm a repository.
    • Run git config --get remote.origin.url to read the remote. Parse owner and repo (HTTPS https://github.com/<owner>/<repo>.git or SSH [email protected]:<owner>/<repo>.git). Only proceed with issue creation when the remote points to github.com.
  • Check for gh with command -v gh >/dev/null 2>&1. If absent, or the remote is not GitHub, or the user is not authenticated (gh auth status fails), skip live creation and write a draft (see Graceful Degradation).

Read the full file on GitHub · 102 lines

Changes

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.

  1. 5d ago Changed · -101 lines · -29 tokens per session 200978ce530e
  2. 8d ago First seen · 102 lines · 29 tokens per session scan A ee8ff4c8d3a4

Subscribe to this mod's changes

speckit-bug-issue is a skill published in the GitHub repository arrrrny/zuraffa (5 stars, last pushed yesterday), licensed MIT. It adds 29 tokens to every session and 1,538 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.

Git and workflowProject managementclean-architectureclicode-generatorflutter
Related

Other skills, from other repositories

create-issue

Draft and submit a GitHub issue from a user idea or bug description, with bilingual body and correct labels.

QwenLM/qwen-code · 26 tokens

gh-assign-issues

Use to assign GitHub issues to a milestone and/or owners in bulk, verifying each.

Hmbown/CodeWhale · 24 tokens

work

Handle issue/PR work items with worktree isolation. Triggered by "/work [issuelink|description]" to start focused work.

x-cmd/x-cmd · 29 tokens

github

Drive GitHub via the official gh CLI — repos, issues, pull requests, releases, gists, Actions runs, and raw REST through gh api. Use when the user asks to inspect or manage GitHub.

AtomicBot-ai/atomic-agent · 48 tokens

parallel-work-check

Apply before starting work on an existing branch. Checks for parallel work by other agents or developers that may supersede or conflict with your planned changes. Prevents wasted effort on stale branches.

ZaxbyHub/opencode-swarm · 41 tokens

github-operations

GitHub CLI operations for issues, PRs, milestones, and Projects v2. Covers gh commands, REST API patterns, and automation scripts. Use when managing GitHub issues, PRs, milestones, or Projects with gh.

yonatangross/orchestkit · 50 tokens