agentmods.dev

zuraffa: Skill for Claude Code

.agents/skills/speckit-bug-test/SKILL.md

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

A workflow for checking whether a previously fixed bug is actually resolved and recording the result.

In plain words
What is it for?
Use it after a bug fix to identify the relevant bug files, run the required validation, and save a test report.
Why use it?
It provides a written verification record instead of relying on an unrecorded manual check.

Skill for Claude CodeCodex

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

This is arrrrny/zuraffa's own configuration. It tells Claude Code and Codex how to work on zuraffa itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything zuraffa configures →

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is - **TDD verification**: ./tdd/verification.md (present only when validation ran in TDD mode).

not rated 5repo changed 3d ago A scan 20 tokens original MIT
View source ↗ arrrrny/zuraffa zuraffa.com
Reuse

Borrowing it

Nothing to install: this file belongs to arrrrny/zuraffa. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/arrrrny/zuraffa/master/.agents/skills/speckit-bug-test/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/arrrrny/zuraffa

Made for: Claude Code, Codex.

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-test

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/arrrrny/zuraffa/speckit-bug-test"><img src="https://agentmods.dev/badge/skills/arrrrny/zuraffa/speckit-bug-test.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 20 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,744 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.00020 $0.01744
Opus 5 $0.00010 $0.00872
Sonnet 5 $0.00004 $0.00349
Haiku 4.5 $0.00002 $0.00174

Measured 3d ago against content hash 8452a35e604c, 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-test 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.

Origin

Copies of this mod

1 near-identical copy found in the catalogue:

.agents/skills/speckit-bug-test/SKILL.md · 141 lines

How it starts

The opening of the file, as written. The whole thing — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Test Bug Fix

Validate that the fix recorded by /speckit-bug-fix actually resolves the bug described by /speckit-bug-assess. The output is a verification report at .specify/bugs/<slug>/test.md.

User Input

$ARGUMENTS

The user input should identify the bug to validate. 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 below).

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 or /speckit-bug-fix, the slug it reported is the working slug. Reuse it without re-prompting. Confirm it by checking that .specify/bugs/<slug>/fix.md exists; if it does not, fall through.
  3. Single candidate on disk — list .specify/bugs/*/fix.md. If exactly one bug has a fix.md, use it.
  4. Disambiguate:
    • Interactive mode: ask the user which bug to validate 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>, and briefly state in your reply which resolution path was used (explicit / from context / single candidate / asked).

Prerequisites

  • BUG_DIR/assessment.md MUST exist.
  • BUG_DIR/fix.md MUST exist. If not, stop and instruct the user to run /speckit-bug-fix first.
  • If BUG_DIR/test.md already exists, ask the user whether to overwrite it (interactive mode) or refuse (automated mode).
  • Read both assessment.md and fix.md in full so you know:
    • The original symptom and reproduction steps (from assessment.md).
    • The actual code changes and tests added (from fix.md).

TDD mode (when tdd_enabled: true in bug-config.yml)

When tdd_enabled is true (the default), validation is driven by the TDD extension's auditor rather than the manual check table:

Read the full file on GitHub · 141 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 · -140 lines · -20 tokens per session f8727ded0776
  2. 9d ago First seen · 141 lines · 20 tokens per session scan A 8452a35e604c

Subscribe to this mod's changes

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

Testingclean-architectureclicode-generatorflutter
Related

Other skills, from other repositories

fl-testing

Writes unit and widget tests for blocs, repositories, and screens using bloctest + mocktail.

phanbaohuy96/flutter_base_structure · 21 tokens

verify

Exercise the real app/API/CLI and collect observable evidence; tests alone do not count as end-to-end verification.

Hmbown/CodeWhale · 25 tokens

dd-triage-flaky-test

Load when investigating a specific flaky test. Gets history, failure pattern, and category, then recommends fix, quarantine, or escalate.

DataDog/pup · 34 tokens

atmos-validation

Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.

cloudposse/atmos · 31 tokens

security-test

Fast, continuous DevSecOps pipeline for Pull Requests and active branches. Runs SAST, SCA, and secrets detection to catch vulnerabilities before they merge.

HoangNguyen0403/agent-skills-standard · 34 tokens

confirm-failures-are-causally-linked-to-the-task-before-reportin

When delegating a task affected by this skill, include.

ZaxbyHub/opencode-swarm · 29 tokens