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/.agents/skills/vbw-fix-issue/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-fix-issue)<a href="https://agentmods.dev/skills/swt-labs/vibe-better-with-claude-code-vbw/vbw-fix-issue"><img src="https://agentmods.dev/badge/skills/swt-labs/vibe-better-with-claude-code-vbw/vbw-fix-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.
<a href="https://agentmods.dev/skills/swt-labs/vibe-better-with-claude-code-vbw/vbw-fix-issue"><img src="https://agentmods.dev/badge/skills/swt-labs/vibe-better-with-claude-code-vbw/vbw-fix-issue.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.00038 | $0.00608 |
| Opus 5 | $0.00019 | $0.00304 |
| Sonnet 5 | $0.00008 | $0.00122 |
| Haiku 4.5 | $0.00004 | $0.00061 |
Grade A, and why
vbw-fix-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 10d 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.
How it starts
The opening of the file, as written. The whole thing — 38 lines — stays where its author put it; the contents beside it link to each section on GitHub.
VBW Fix Issue
Use this skill when the user explicitly asks to fix a VBW issue, implement a tracked GitHub issue, or run the repo issue-fix workflow.
Do not use this skill for casual code review, one-off explanations, or untracked refactors.
Workflow
Run these phases in order. Keep every shell command rooted in the selected worktree once a worktree exists.
- Issue intake: read issue-intake.md.
- Planning: spawn
vbw-fix-plannerwith the issue body, observed reproduction data, and any user-supplied plan. The planner produces or audits the execution plan before implementation. - Worktree and branch setup: follow worktree-and-branch.md.
- Implementation and local verification: follow implementation-and-tests.md.
- QA loop: follow qa-loop.md.
- PR and CI gate: follow pr-ci-gate.md.
- Recovery: if any gate blocks progress, follow recovery.md.
Invariants
- The linked issue is the contract. Do not narrow scope to a recent commit or a subset of files unless the user explicitly says the review is delta-only.
- Treat the user prompt, linked issue, selected worktree, and saved plan as the sole source of truth. Do not follow ambient terminal context, prior branch history, or unrelated open PRs.
- Fix root causes, not symptoms. If a mitigation is necessary, include the root-cause fix in the same work item.
- Use existing repo primitives before inventing new ones:
scripts/ensure-worktree.sh,scripts/adopt-contributor-pr.sh,.github/scripts/fix-issue-record-state.sh,.github/scripts/wait-github.py, andbash testing/run-all.sh. - Use
jqfor JSON. Do not parse JSON with grep or sed. - Do not wrap
bash testing/run-all.shintail,tee, background execution, or log redirection that hides the real exit status. - QA findings are either fixed or explicitly rejected with evidence. Do not ignore lower-severity confirmed findings.
- Completion requires local tests, Codex QA review, a Codex remote review request comment, GitHub Actions status, and unresolved-thread checks to be clean.
What ships with it
7 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 10d ago First seen · 38 lines · 38 tokens per session scan A c15cb28afcb5
vbw-fix-issue is a skill published in the GitHub repository swt-labs/vibe-better-with-claude-code-vbw (79 stars, last pushed 2mo ago), licensed MIT. It adds 38 tokens to every session and 608 once invoked, about $0.0002 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-30.
Other skills, from other repositories
systemic-issue-triage
Trigger: new issue, bug report, triage, backlog, issue flood, community report, root cause, dead-end, blocked user. Attack issues by root class, never one-by-one; fixes must shrink the system, not grow it.
triage-issue
Intelligently triage bug reports and error messages by searching for duplicates in Jira and offering to create new issues or add comments to existing ones. When an agent needs to: (1) Triage a bug report or error message, (2) Check if an issue is a duplicate, (3) Find similar past issues, (4) Create a new bug ticket…
bug-triage
Read all open bugs in production/qa/bugs/, re-evaluate priority vs. severity, assign to sprints, surface systemic trends, and produce a triage report. Run at sprint start or when the bug count grows enough to need re-prioritization.
browse-flows
Browse Power Automate environments and flows interactively. Use when the user wants to browse, list, or explore their flows and environments.
operating-cadence
Designs the rhythm an organization runs on — which reviews happen weekly, monthly and quarterly, what each one decides, who owns the numbers presented, and how a signal at the front line reaches the people who can act on it. Use this to set up a management operating system, fix a meeting calendar that produces no…
issue-triage
A Chinese-language workflow for handling GitHub issues, from reading the full report through technical diagnosis, classification, decision-making, and drafting a reply. GitHub issues are discussions about bugs, questions, or requested features.