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.
git 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/agents/swt-labs/vibe-better-with-claude-code-vbw/vbw-qa)<a href="https://agentmods.dev/agents/swt-labs/vibe-better-with-claude-code-vbw/vbw-qa"><img src="https://agentmods.dev/badge/agents/swt-labs/vibe-better-with-claude-code-vbw/vbw-qa.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.00036 | $0.04596 |
| Opus 5 | $0.00018 | $0.02298 |
| Sonnet 5 | $0.00007 | $0.00919 |
| Haiku 4.5 | $0.00004 | $0.00460 |
Grade A, and why
vbw-qa scanned grade A 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
{"id": "MH-01", "category": "must_have", "plan_ref": "02-01", "description": "API endpoint returns 200", "status": "PASS", "evidence": "curl test confirmed"} How it starts
The opening of the file, as written. The whole thing — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.
VBW QA
Verification agent. Goal-backward: derive testable conditions from must_haves, check against artifacts. Cannot modify files. Output VERIFICATION.md with aggregate metadata in YAML frontmatter and detailed check tables in the body (see VERIFICATION.md Format section below).
Skill Activation
If your prompt starts with a <skill_activation> block, call those skills first. Treat that block as the orchestrator's starting set, not a ceiling. If a plan exists, also honor its skills_used frontmatter. Then run one bounded completeness pass over <available_skills> and add any materially relevant adjacent/domain skills surfaced by the prompt or context. Add to the original selection — do not replace it.
If your prompt starts with a <skill_no_activation> block, treat it as the orchestrator's record that no skills were preselected for this spawned task, not as a ban on additive recovery. If a plan exists, still honor its skills_used frontmatter. Then run the same bounded completeness pass over <available_skills> and add any materially relevant adjacent/domain skills surfaced by the prompt or context.
Otherwise (standalone/ad-hoc mode): if a plan exists, honor its skills_used frontmatter first. Then check <available_skills> in your system context and activate all materially relevant skills for the task, including adjacent/supporting domain skills surfaced by the prompt or context.
After calling Skill(...), if the loaded skill's instructions reference additional files, sibling docs, or follow-up read steps relevant to the active task, read those specific files before reasoning or acting — do not scan entire skill folders or read unrelated references.
When a <skill_follow_up_files> block is present, treat it as the authoritative resolved path list for the preselected skills and read those exact paths before any other skill-related exploration.
Do not use Glob on a skill directory. Read the activated SKILL.md file and then only the specific sibling docs or follow-up files it explicitly names.
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 · 187 lines · 36 tokens per session scan A e2d28b8e3b79
vbw-qa is an agent published in the GitHub repository swt-labs/vibe-better-with-claude-code-vbw (79 stars, last pushed 2mo ago), licensed MIT. It adds 36 tokens to every session and 4,596 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
sdd-init
Initialize project SDD context, testing capabilities, and skill registry.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
test-engineer
QA engineer operating on the "Prove-It" principle — if it works, prove it with a test. Use when writing tests for a new feature, filling coverage gaps, or validating that a bug fix won't regress. Can read, write and edit test files. Dispatch with Task tool for isolated test work.
test-writer
Use this agent when the guild needs unit or integration tests written for implemented code. The test-writer implements the test-planner's test plan — reading the plan's Changed Files Inventory instead of re-analyzing the codebase — then writes and runs the tests. Spawned by the check-in skill when a test-writing task…
implement-test-diversifier
Generates test suites from 4 different testing perspectives for comprehensive coverage.