Borrowing it
Nothing to install: this file belongs to swt-labs/vibe-better-with-claude-code-vbw. 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/swt-labs/vibe-better-with-claude-code-vbw/main/.claude/skills/vbw-debug-target/SKILL.mdgit clone --depth 1 https://github.com/swt-labs/vibe-better-with-claude-code-vbwWrote 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/swt-labs/vibe-better-with-claude-code-vbw/vbw-debug-target)<a href="https://agentmods.dev/skills/swt-labs/vibe-better-with-claude-code-vbw/vbw-debug-target"><img src="https://agentmods.dev/badge/skills/swt-labs/vibe-better-with-claude-code-vbw/vbw-debug-target/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/swt-labs/vibe-better-with-claude-code-vbw/vbw-debug-target"><img src="https://agentmods.dev/badge/skills/swt-labs/vibe-better-with-claude-code-vbw/vbw-debug-target.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.00070 | $0.01298 |
| Opus 5.5 | $0.00028 | $0.00519 |
| Sonnet 5.5 | $0.00014 | $0.00260 |
| Haiku 4.5 | $0.00007 | $0.00130 |
Grade A, and why
vbw-debug-target 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 today.
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.
How it starts
The opening of the file, as written. The whole thing — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debugging VBW behavior
When the user reports VBW misbehavior — pasting Claude Code session output, describing incorrect command behavior, or showing unexpected file state — first resolve the contributor's local debug target repo instead of guessing a maintainer-specific path.
Local debug target configuration (private, not committed)
Preferred setup in the VBW clone's shared Git common dir:
$(git rev-parse --git-common-dir)/info/vbw-debug-target.txt
In a standard non-worktree clone, this usually resolves to:
.git/info/vbw-debug-target.txt
The first non-empty, non-comment line must be the absolute path to the contributor's primary VBW consumer/test repo. Relative paths are rejected so the resolver produces the same result regardless of the caller's current working directory.
Example local file content:
/absolute/path/to/your-test-repo
This file lives under the clone's shared Git metadata, so it stays private and all worktrees created from that clone can read it automatically.
Legacy fallback for a single checkout only:
.claude/vbw-debug-target.txt
That legacy file remains supported and gitignored, but it is scoped to one checkout/worktree and will not be copied into new worktrees.
Resolution order:
VBW_DEBUG_TARGET_REPOenv var (one-off override, absolute path only)$(git rev-parse --git-common-dir)/info/vbw-debug-target.txtin the current clone (preferred persistent local config, shared across worktrees)./.claude/vbw-debug-target.txtin the current checkout/worktree (legacy fallback, absolute path only)<claude-config-dir>/vbw/debug-target.txt(user-global fallback, absolute path only;<claude-config-dir>is resolved bytools/resolve-claude-dir.sh:CLAUDE_CONFIG_DIRif set, else$HOME/.config/claude-codewhen that directory exists, else$HOME/.claude)- If none are configured, ask the user for the target repo path — do not guess.
Use the shared resolver when debugging:
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.
- today First seen · 109 lines · 70 tokens per session scan A 29580e0e6009
vbw-debug-target is a skill published in the GitHub repository swt-labs/vibe-better-with-claude-code-vbw (85 stars, last pushed today), licensed MIT. It adds 70 tokens to every session and 1,298 once invoked, about $0.0003 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-22.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
deck-retro
Run a fully local agent-deck retrospective over the user's own transcripts, Recall index and logs. Use when a user wants to find recurring failures or take their own finding from investigation through synthetic reproduction, a user-filed issue, a test-first fix and contributor PR handoff. Also use for weekly usage…
incident-response-incident-response
Coordinate production incident triage, mitigation, investigation, recovery, and follow-up. Use when responding to outages or other incidents that require structured operational coordination.
cwv-optimizer
Diagnose and fix Core Web Vitals issues on AEM Edge Delivery Services pages. Goes deeper than generic CWV advice by understanding EDS-specific performance patterns including the 100KB LCP budget, E-L-D loading phases, block rendering behavior, and third-party script impact. Produces specific fixes for LCP, CLS, and…