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/.github/skills/running-ccr-smoke-tests/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/running-ccr-smoke-tests)<a href="https://agentmods.dev/skills/swt-labs/vibe-better-with-claude-code-vbw/running-ccr-smoke-tests"><img src="https://agentmods.dev/badge/skills/swt-labs/vibe-better-with-claude-code-vbw/running-ccr-smoke-tests/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/running-ccr-smoke-tests"><img src="https://agentmods.dev/badge/skills/swt-labs/vibe-better-with-claude-code-vbw/running-ccr-smoke-tests.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.00067 | $0.03755 |
| Opus 5 | $0.00034 | $0.01878 |
| Sonnet 5 | $0.00013 | $0.00751 |
| Haiku 4.5 | $0.00007 | $0.00376 |
Grade A, and why
running-ccr-smoke-tests 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 11d 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.
This is a copy
91% identical to running-claude-smoke-tests — 127 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 306 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Running CCR smoke tests
Use this skill when validating VBW behavior with ccr code so future issue-fix runs do not have to rediscover the router entrypoint, the consumer repo path, or the provenance checks.
Core rule
- Do not run the smoke test with the VBW plugin repo or plugin worktree as the working directory.
- Do not run the smoke test directly in the base consumer repo checkout.
- Create or reuse a disposable consumer smoke worktree and run
ccr codethere, or use a sandbox repo when the real consumer repo cannot exercise the flow. - Use the candidate VBW checkout only as
--plugin-dir. - If the smoke needs installed skill fixtures, seed them only under the consumer repo's
.claude/skills/<skill>/tree or the global Claude configskills/directory after sourcingscripts/resolve-claude-dir.shand using${CLAUDE_DIR}. Do not use.agents/or.pi/as positive fixtures. - When documenting results, say: "smoke-tested from a consumer smoke worktree or sandbox while loading the candidate plugin checkout via
--plugin-dir". - If the transcript path encodes the plugin repo or the base consumer repo checkout instead of the consumer smoke worktree/sandbox, treat the smoke result as suspect until proven otherwise.
Expected inputs
- Candidate plugin checkout path, usually the current VBW worktree under test.
- Preferred consumer repo path, resolved from the VBW checkout with:
bash scripts/resolve-debug-target.sh repo
- Smoke worktree label such as
smoke-fix-issue-502orsmoke-skill-audit. - Optional sandbox path such as
/tmp/vbw-skill-smoke-<issue>for phase-routed flows the real consumer repo cannot exercise.
Location roles
Keep these four locations distinct throughout the run:
- Candidate plugin checkout — the VBW repo checkout under test. Pass this path only through
--plugin-dir. - Consumer repo — the real target repo used to resolve the testing target and create/remove the smoke worktree. Do not run
ccr codefrom this checkout. - Consumer smoke worktree — the disposable worktree created from the consumer repo. This is the real cwd for consumer-repo smoke tests.
- Sandbox repo — a temporary repo used only when the consumer repo cannot exercise the required phase-routed flow.
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.
- 11d ago First seen · 306 lines · 67 tokens per session scan A 1a5b399c7753
running-ccr-smoke-tests 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 67 tokens to every session and 3,755 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to running-claude-smoke-tests, differing in 127 lines, and is treated as a copy.
Other skills, from other repositories
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
tika-eval-compare
Compare extracts from two Tika builds over a corpus to detect regressions in content, encoding, exceptions, and embedded-document handling. Use for "compare before/after extracts", "eval this change against the corpus".
neuron-evaluation-engineer
Create and run AI evaluations with datasets, assertions, and output drivers in Neuron AI. Use this skill whenever the user mentions evaluation, testing AI systems, creating evaluators, dataset-driven testing, assertion-based validation, or wants to measure AI system performance. Also trigger for tasks involving…
jetson-validate-image
Use after jetson-flash-image to run static BSP checks, on-target smoke/regression tests on a flashed DUT, or both. Not for build or flash steps. Triggers: validate bsp, on-target validation.
atmos-validation
Validate Atmos projects, components, arbitrary JSON Schema inputs, EditorConfig, and GitHub Actions; use affected-file selection and native CI annotations.
skill-benchmark
Benchmark AI skill effectiveness by measuring implementation quality against legacy constraints.