Borrowing it
Nothing to install: this file belongs to Badminton-Apps/badman. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Badminton-Apps/badman/develop/.claude/skills/speckit-bug-test/SKILL.mdgit clone --depth 1 https://github.com/Badminton-Apps/badmanWrote 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/badminton-apps/badman/speckit-bug-test)<a href="https://agentmods.dev/skills/badminton-apps/badman/speckit-bug-test"><img src="https://agentmods.dev/badge/skills/badminton-apps/badman/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.
<a href="https://agentmods.dev/skills/badminton-apps/badman/speckit-bug-test"><img src="https://agentmods.dev/badge/skills/badminton-apps/badman/speckit-bug-test.svg" alt="Reviewed on agentmods" width="80" 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.00020 | $0.01399 |
| Opus 5.5 | $0.00008 | $0.00560 |
| Sonnet 5.5 | $0.00004 | $0.00280 |
| Haiku 4.5 | $0.00002 | $0.00140 |
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 9d 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
2 near-identical copies found in the catalogue:
- speckit-bug-test — 92% identical, 2 lines differ
- speckit-bug-test — 89% identical, 29 lines differ
How it starts
The opening of the file, as written. The whole thing — 122 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:
- Explicit user input — a slug passed in
$ARGUMENTS(any of the forms above). - Conversation context — if the current session has just run
/speckit-bug-assessor/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.mdexists; if it does not, fall through. - 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 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.mdMUST exist.BUG_DIR/fix.mdMUST exist. If not, stop and instruct the user to run/speckit-bug-fixfirst.- If
BUG_DIR/test.mdalready exists, ask the user whether to overwrite it (interactive mode) or refuse (automated mode). - Read both
assessment.mdandfix.mdin full so you know:- The original symptom and reproduction steps (from
assessment.md). - The actual code changes and tests added (from
fix.md).
- The original symptom and reproduction steps (from
Execution
- Plan the validation
- Decide which checks prove the bug is gone:
- Re-run the reproduction steps from the assessment (or their automated equivalent).
- Run the tests added or updated in the fix.
- Run any broader regression suite that touches the changed files.
- Decide which checks prove nothing was broken:
- Existing test suites for the changed modules.
- Lint / type-check if the project uses them.
- Decide which checks prove the bug is gone:
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.
- 9d ago First seen · 122 lines · 20 tokens per session scan A 2acdf15daf90
speckit-bug-test is a skill published in the GitHub repository Badminton-Apps/badman (13 stars, last pushed 2d ago), licensed Apache-2.0. It adds 20 tokens to every session and 1,399 once invoked, about $0.0001 per session on Opus 5.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-10-12.
Other skills, from other repositories
systematic-debugging
4-phase root cause debugging: understand bugs before fixing.
langsmith-observability
LLM observability platform for tracing, evaluation, and monitoring. Use when debugging LLM applications, evaluating model outputs against datasets, monitoring production systems, or building systematic testing pipelines for AI applications.
test-failure-explorer
Import and query an existing Vitest 3.2 JSON report to explore test failures, file-level errors and original diagnostic evidence.
experimental-code-coverage-local-debugger
Runs code coverage locally via Universal Test Runner (UTR) or helper scripts, mimicking LUCI trybots. Activate when CQ tryjobs fail or underreport coverage, to test local GN/recipe repairs before uploading, or to debug hermetic crashes.
verify-omnigent
Drive Omnigent the way a user does and prove a behavior with recorded evidence, using an isolated server, runner, and mock model plus a feature map of every user entry point. Load before reproducing a user-facing bug, before claiming a fix works, or when reviewing whether a change covered every surface (session vs.…
cli-e2e
Write, modify, or debug Docker-based Composio CLI end-to-end tests under ts/e2e-tests/cli, including binary invocation, fixture isolation, output assertions, and package manifests. Use for CLI E2E test suites only; use cli-command for CLI source implementation.