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.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/instructions/swt-labs/vibe-better-with-claude-code-vbw/agents-md)<a href="https://agentmods.dev/instructions/swt-labs/vibe-better-with-claude-code-vbw/agents-md"><img src="https://agentmods.dev/badge/instructions/swt-labs/vibe-better-with-claude-code-vbw/agents-md.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.05343 | $0.05343 |
| Opus 5 | $0.02671 | $0.02671 |
| Sonnet 5 | $0.01069 | $0.01069 |
| Haiku 4.5 | $0.00534 | $0.00534 |
Grade C, and why
vibe-better-with-claude-code-vbw AGENTS.md 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 8d 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.
- **Toggle**: Edit `~/.claude-code-router/config.json` and set `CLAUDE_PATH` to one of the above. Optionally `rm -rf "${CLAUDE_CONFIG_DIR:-$HOME/.claude}/commands/vbw"` before relaunching to clear stale command cache. How it starts
The opening of the file, as written. The whole thing — 333 lines — stays where its author put it; the contents beside it link to each section on GitHub.
VBW Instructions
A Claude Code plugin adding structured development workflows (plan → execute → verify) via 7 specialized agent teams. Zero external dependencies beyond jq and git. All logic is bash scripts + markdown.
Communication Style
- No AI fluff. Skip phrases like "Thanks for the thoughtful feedback!", "Happy to help!", "I appreciate...", etc.
- No soliciting opinions. Don't end responses with "Would you like me to...", "Let me know if...", "What do you think?", etc.
- Direct and terse. State facts, provide options when relevant, then stop.
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 byscripts/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.
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.
- 8d ago First seen · 333 lines · 5,343 tokens per session scan C 4d4229ac27ab
vibe-better-with-claude-code-vbw AGENTS.md is an instructions file published in the GitHub repository swt-labs/vibe-better-with-claude-code-vbw (79 stars, last pushed 2mo ago), licensed MIT. It adds 5,343 tokens to every session, about $0.0267 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 instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.