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 skills add wedabro/bro-skills --skill speckit.debuggit clone --depth 1 https://github.com/wedabro/bro-skillsWrote 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/wedabro/bro-skills/speckit.debug)<a href="https://agentmods.dev/skills/wedabro/bro-skills/speckit.debug"><img src="https://agentmods.dev/badge/skills/wedabro/bro-skills/speckit.debug.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.00023 | $0.00349 |
| Opus 5 | $0.00012 | $0.00175 |
| Sonnet 5 | $0.00005 | $0.00070 |
| Haiku 4.5 | $0.00002 | $0.00035 |
Grade A, and why
speckit.debug 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 6d 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.
What it actually says
🎯 Mission
Use scientific methodology to find the root cause of bugs without disturbing the main context of feature development.
📋 Protocol
Phase 1: Symptom Gathering (Symptom collection)
Before starting to code, make it clear:
- Expected behavior: What is the expected result?
- Actual behavior: What is the actual result that is happening?
- Error messages: Specific error logs (paste directly).
- Reproduction: Specific steps to reproduce the error (required).
Phase 2: Isolation & Hypothesis (Isolation & Hypothesis)
- Create file
.agents/debug/[issue-slug].mdto save the investigation log. - Hypotheses: "Maybe the error lies in function X because of Y".
- Use the commands
grep,logto verify the hypothesis.
Phase 3: Root Cause Found (Determine the cause)
- Only end the investigation when the specific line of code/configuration causing the error is found.
- Explain WHY it fails instead of just saying IT IS ERROR.
Phase 4: Fix Proposal (Proposal to fix errors)
- Do not correct errors directly in this skill.
- The output is either a proposed fix or the creation of a
gap_planforspeckit.implementto execute.
🚫 Guard Rails
- NO guessing. Every conclusion must have evidence from logs or code.
- DO NOT further damage existing code during debugging (use Read-only tools mainly).
- MUST create a debug log file to save traces.
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.
- 6d ago First seen · 35 lines · 23 tokens per session scan A 6be2dd754e22
speckit.debug is a skill published in the GitHub repository wedabro/bro-skills (2 stars, last pushed 10d ago), licensed MIT. It adds 23 tokens to every session and 349 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 skills, from other repositories
winui-session-report
Analyze the current or a recent agent session (GitHub Copilot CLI or Claude Code) and generate a diagnostic report. Use only when the user explicitly asks for session feedback, agent debugging, or a review of what happened during a build session. Do not inspect session data automatically.
spm-build-analysis
Analyze Swift Package Manager dependencies, package plugins, module variants, and CI-oriented build overhead that slow Xcode builds. Use when a developer suspects packages, plugins, or dependency graph shape are hurting clean or incremental build performance, mentions SPM slowness, package resolution time, build…
investigate
Systematically investigate bugs, test failures, build errors, performance issues, or unexpected behavior by cycling through characterize-isolate-hypothesize-test steps. Use when the user asks to "investigate this bug", "debug this", "figure out why this fails", "find the root cause", "why is this broken"…
audit
Project-wide health audit pipeline that fans out to all analysis skills in parallel, evaluates findings, and produces a unified report at .turbo/audit.md. Use when the user asks to "audit the project", "run a full audit", "project health check", "audit my code", "codebase audit", or "comprehensive review".
consult-oracle
Consult ChatGPT Pro via ChatGPT browser automation for problems that resist standard approaches. Use when stuck on a very hard problem, when standard approaches have failed, when multiple debugging attempts haven't worked, or when the user says "ask the oracle", "consult oracle", "consult chatgpt", "I'm completely…
webflow-code-component:troubleshoot-deploy
Debug deployment failures for Webflow Code Components. Analyzes error messages, identifies root causes, and provides specific fixes for common issues.