agentmods.dev

vibe-better-with-claude-code-vbw: Instructions file for Claude Code

.github/copilot-instructions.md

vibe-better-with-claude-code-vbw copilot-instructions.md is an instructions file for Claude Code, GitHub Copilot from swt-labs/vibe-better-with-claude-code-vbw. It costs 736 tokens per session, scanned A, original, MIT.

Instructions for GitHub Copilot's cloud coding agent in the Vibe Better with Claude Code project. They describe the repository layout, editing conventions, hooks, commands, and contract tests.

In plain words
What is it for?
Use them when Copilot modifies slash commands, shell scripts, hooks, templates, references, or tests in this repository.
Why use it?
They help the agent change the right files and preserve behaviors checked by the project's tests.

Instructions file for Claude CodeGitHub Copilot

Written for Claude Code and GitHub Copilot: ${CLAUDE_PLUGIN_ROOT} variable, but also a Copilot instructions file. Also seen: mentions Claude Code.

This is swt-labs/vibe-better-with-claude-code-vbw's own configuration. It tells Claude Code and GitHub Copilot how to work on vibe-better-with-claude-code-vbw itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything vibe-better-with-claude-code-vbw configures →

Runs only inside a plugin — its command needs a path that Claude Code sets for a plugin’s own hooks and for nothing else, and the catalogue could not identify which plugin ships it.

not rated 79repo +1 2mo ago A scan 736 tokens original MIT
View source ↗ swt-labs/vibe-better-with-claude-code-vbw
Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/swt-labs/vibe-better-with-claude-code-vbw/main/.github/copilot-instructions.md
Clone the repo
git clone --depth 1 https://github.com/swt-labs/vibe-better-with-claude-code-vbw

Made for: Claude Code, GitHub Copilot.

Wrote 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.

agentmods badge for vibe-better-with-claude-code-vbw copilot-instructions.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/swt-labs/vibe-better-with-claude-code-vbw/copilot-instructions.svg)](https://agentmods.dev/instructions/swt-labs/vibe-better-with-claude-code-vbw/copilot-instructions)
Your own site
<a href="https://agentmods.dev/instructions/swt-labs/vibe-better-with-claude-code-vbw/copilot-instructions"><img src="https://agentmods.dev/badge/instructions/swt-labs/vibe-better-with-claude-code-vbw/copilot-instructions.svg" alt="Measured on agentmods" height="20"></a>
Per session 736 This file is loaded in full into every session.
When invoked 736 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00736 $0.00736
Opus 5 $0.00368 $0.00368
Sonnet 5 $0.00147 $0.00147
Haiku 4.5 $0.00074 $0.00074

Measured 8d ago against content hash b6152dab9e8e, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

vibe-better-with-claude-code-vbw copilot-instructions.md 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 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.

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.

.github/copilot-instructions.md · 34 lines

How it starts

The opening of the file, as written. The whole thing — 34 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Copilot cloud agent instructions for VBW

Start here

  • Read README.md first, then CONTRIBUTING.md, then the relevant files under commands/, scripts/, testing/, hooks/, templates/, or references/.
  • This repo is a Claude Code plugin implemented mostly as bash plus command markdown. There is no normal app build; most changes are to shell scripts, slash-command markdown, hook wiring, templates, and tests.
  • Keep changes surgical. Many behaviors are enforced by contract tests that grep for exact phrases, tool names, filenames, and command structure.

Repo shape

  • commands/*.md: slash-command definitions with YAML frontmatter. Preserve frontmatter shape, explicit name: vbw:*, and the repo's direct/dry tone.
  • scripts/*.sh and scripts/lib/*.sh: runtime logic. Prefer reusing existing helpers instead of adding new one-off patterns.
  • hooks/hooks.json: plugin hook wiring. Hooks must degrade gracefully; they should not break a Claude Code session.
  • testing/ and tests/: contract checks and bats coverage. If you change behavior, inspect the matching testing/verify-*.sh file before editing.
  • .claude-plugin/plugin.json, VERSION, .claude-plugin/marketplace.json, and marketplace.json: keep versions aligned only when intentionally doing a release/version task. Do not bump versions for ordinary fixes.

Working conventions

  • Prefer bash and existing repo utilities. Do not introduce Node/Python/Ruby tooling or new dependencies unless the task explicitly requires it.
  • Preserve the plugin-root resolution pattern already used in command markdown and hooks. In shell blocks, do not assume ${CLAUDE_PLUGIN_ROOT} exists as a normal environment variable; reuse the existing /tmp/.vbw-plugin-root-link-${CLAUDE_SESSION_ID:-default} / ensure-plugin-root-link.sh pattern instead of inventing a new resolver.
  • When editing command markdown, remember the command files are LLM-consumed artifacts. Small wording changes can break tests or behavior.
  • If you change command or hook behavior, search testing/ for the corresponding contract before editing. The test usually documents the intended invariant better than a quick skim of the implementation.
  • Keep the repo zero-dependency in spirit: portable bash, jq, git, and the existing test tools.

Read the full file on GitHub · 34 lines

Changes

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.

  1. 8d ago First seen · 34 lines · 736 tokens per session scan A b6152dab9e8e

Subscribe to this mod's changes

vibe-better-with-claude-code-vbw copilot-instructions.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 736 tokens to every session, about $0.0037 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.

Related

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.

vercel/next.js · 7,296 tokens

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.

openai/codex · 5,153 tokens

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).

microsoft/vscode · 6,785 tokens

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).

microsoft/vscode · 5,001 tokens

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.

langchain-ai/langchain · 4,469 tokens

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.

github/spec-kit · 7,104 tokens