Borrowing it
Nothing to install: this file belongs to mtarcure/claude-vibe-squad. 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/mtarcure/claude-vibe-squad/main/CLAUDE.mdgit clone --depth 1 https://github.com/mtarcure/claude-vibe-squadWrote 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/mtarcure/claude-vibe-squad/claude-md)<a href="https://agentmods.dev/instructions/mtarcure/claude-vibe-squad/claude-md"><img src="https://agentmods.dev/badge/instructions/mtarcure/claude-vibe-squad/claude-md/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/instructions/mtarcure/claude-vibe-squad/claude-md"><img src="https://agentmods.dev/badge/instructions/mtarcure/claude-vibe-squad/claude-md.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.01585 | $0.01585 |
| Opus 5 | $0.00792 | $0.00792 |
| Sonnet 5 | $0.00317 | $0.00317 |
| Haiku 4.5 | $0.00159 | $0.00159 |
Grade A, and why
claude-vibe-squad CLAUDE.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 today.
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.
How it starts
The opening of the file, as written. The whole thing — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Vibe Squad Root Instructions
Vibe Squad is markdown-first:
Operator -> Chrono -> gpt-codex | claude | gemini | kimi | grok -> specialists
Chrono is the only controller and the only operator-facing voice. Model leads execute scoped markdown task packets. Source namespaces under departments/ locate specialist/role markdown only; they do not determine model choice.
Canonical Sources
- Routing:
shared/specialist-runtime-map.tsv - Dispatch protocol:
shared/protocol.md - Runtime rules:
shared/routing.md - Mode workflows:
shared/modes/*.md - Specialist behavior:
departments/*/specialists/*.mdandshared/specialists/*.md - Model lead prompts:
model-lanes/* - Durable memory: private markdown vault via
chrono-vault(record/recall); seeplugins/chrono-vault/README.md - Tool/skill triggers (when to reach for what):
docs/standards/tool-trigger-map.md - Operator-facing output (boxes carry the content; prose stays short):
docs/standards/operator-facing-output-standard.md— internal-only; withheld from the public export, with no public equivalent shipped
Generated adapters, stale handoffs, old specs, and runtime logs are not source of truth. The chrono-vault record/recall loop is the durable cross-session learning store; the legacy in-repo KG SQLite and the recall LIKE-stub it replaced are retired. The chrono-kg MCP namespace remains live as a compatibility alias backed by those canonical Markdown-vault operations; it does not revive SQLite.
Versions — three numbering systems, all real
Confusing these is the single most common source of "is this doc out of date?" in this repo.
V1.1.6is the current release version. Git tags runv1.1.0throughv1.1.5, withv1.1.6applied tomainby Chrono as this release is cut; the next upgrade would beV1.1.7. This is the version of the system as a product.V3/V4are architecture generations, not old release numbers. Git tagsv3-finalandv4-baseline-2026-08-07. The dispatcher still runs a live V3 compatibility bridge, soshared/protocol.mdsaying "the staged V4 boundary" is current, not stale. Renaming these toV1.1.1would destroy a real distinction.contract/v1,dispatch-preflight/v1and friends are schema identifiers that code parses. Never touch them.
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.
- today Changed · +1 lines · +41 tokens per session 1c87426a6231
- 5d ago First seen · 71 lines · 1,544 tokens per session scan A b9ab1d097025
claude-vibe-squad CLAUDE.md is an instructions file published in the GitHub repository mtarcure/claude-vibe-squad (122 stars, last pushed today), licensed MIT. It adds 1,585 tokens to every session, about $0.0079 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-09-03.
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.