Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add swt-labs/vibe-better-with-claude-code-vbw/plugin install 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/commands/swt-labs/vibe-better-with-claude-code-vbw/uninstall)<a href="https://agentmods.dev/commands/swt-labs/vibe-better-with-claude-code-vbw/uninstall"><img src="https://agentmods.dev/badge/commands/swt-labs/vibe-better-with-claude-code-vbw/uninstall/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/commands/swt-labs/vibe-better-with-claude-code-vbw/uninstall"><img src="https://agentmods.dev/badge/commands/swt-labs/vibe-better-with-claude-code-vbw/uninstall.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.00600 |
| Opus 5 | $0.00010 | $0.00300 |
| Sonnet 5 | $0.00004 | $0.00120 |
| Haiku 4.5 | $0.00002 | $0.00060 |
Grade C, and why
vbw:uninstall scanned grade C with 1 finding 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
If `.vbw-planning/` exists: ask keep (recommended) or delete. Delete: `rm -rf .vbw-planning/`. What it actually says
VBW Uninstall
Context
Settings:
!`for _d in "${CLAUDE_CONFIG_DIR:-}" "$HOME/.config/claude-code" "$HOME/.claude"; do [ -z "$_d" ] && continue; [ -f "$_d/settings.json" ] && cat "$_d/settings.json" 2>/dev/null && break; done || echo "{}"`
Planning dir:
!`ls -d .vbw-planning 2>/dev/null && echo "EXISTS" || echo "NONE"`
CLAUDE.md:
!`ls CLAUDE.md 2>/dev/null && echo "EXISTS" || echo "NONE"`
Steps
Resolve config directory: Try in order: env var CLAUDE_CONFIG_DIR (if set and directory exists), ~/.config/claude-code (if exists), otherwise ~/.claude. Store result as CLAUDE_DIR.
Step 1: Confirm intent
Display Phase Banner "VBW Uninstall" explaining system-level config removal. Project files handled separately. Ask confirmation.
Step 2: Clean statusLine
Read CLAUDE_DIR/settings.json. If statusLine contains vbw-statusline: remove entire statusLine key, display ✓. If not VBW's: "○ Statusline is not VBW's — skipped".
Step 3: Clean Agent Teams env var
If env.CLAUDE_CODE_EXPERIMENTAL_AGENT_TEAMS exists: ask user (it's a Claude Code feature other tools may use). Approved: remove (if env then empty, remove env key). Declined: "○ Agent Teams setting kept".
Step 4: Project data
If .vbw-planning/ exists: ask keep (recommended) or delete. Delete: rm -rf .vbw-planning/.
Step 5: CLAUDE.md cleanup
If CLAUDE.md exists: ask keep or delete.
Step 6: Summary
Display Phase Banner "VBW Cleanup Complete" with ✓/○ per step. Then:
➜ Final Step
/plugin uninstall vbw@vbw-marketplace
Then optionally: /plugin marketplace remove vbw-marketplace
Do NOT run plugin uninstall yourself — it would remove itself mid-execution.
Output Format
Follow @${CLAUDE_PLUGIN_ROOT}/references/vbw-brand-essentials.md — Phase Banner (double-line box), ✓ completed, ○ skipped, Next Up, no ANSI.
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 · 64 lines · 20 tokens per session scan C 4ecadd329574
vbw:uninstall is a command published in the GitHub repository swt-labs/vibe-better-with-claude-code-vbw (79 stars, last pushed 2mo ago), licensed MIT. It adds 20 tokens to every session and 600 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.