Borrowing it
Nothing to install: this file belongs to jubayertalha/vibeframe. 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/jubayertalha/vibeframe/main/CLAUDE.mdgit clone --depth 1 https://github.com/jubayertalha/vibeframeWrote 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/jubayertalha/vibeframe/claude-md)<a href="https://agentmods.dev/instructions/jubayertalha/vibeframe/claude-md"><img src="https://agentmods.dev/badge/instructions/jubayertalha/vibeframe/claude-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.00712 | $0.00712 |
| Opus 5 | $0.00356 | $0.00356 |
| Sonnet 5 | $0.00142 | $0.00142 |
| Haiku 4.5 | $0.00071 | $0.00071 |
Grade A, and why
vibeframe 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 6d 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.
How it starts
The opening of the file, as written. The whole thing — 46 lines — stays where its author put it; the contents beside it link to each section on GitHub.
VibeFrame — repository guide
VibeFrame is a control plane for agentic coding: a living, in-repo model of intent,
architecture, and code (.vibeframe/), deterministically indexed, bidirectionally linked,
continuously checked for drift. The approved Discovery report is the product baseline;
docs/ mirrors its decisions. The framework makes zero LLM calls — the coding agent is
the only intelligence, connected via MCP.
Layout
packages/core— model schemas (zod),.vibeframe/store, schema versioning + migrations, IDs, errors, loggingpackages/store— SQLite (better-sqlite3): code plane, link state, events, findings, reconcile queuepackages/indexer— tree-sitter (WASM) symbols, import resolution (oxc-resolver + Python resolver), watcher, git catch-uppackages/engine— graphology working graph, lenses, impact analysis, reflexion validator, digest builderpackages/daemon— hono app: MCP endpoint (Streamable HTTP) + REST + SSE + UI hostingpackages/cli—vibeframebin: init/start/stop/status/index/validate/mcp/hook; ships built UI inui-dist/packages/ui— React 19 + React Flow lens UI (private; builds intopackages/cli/ui-dist)plugin/— Claude Code plugin (manifest, hooks, skills, commands, dependency-free launchers)tests/dogfood— end-to-end acceptance scenarios;examples/restaurant-platformis their fixture
Dependency direction (enforced by tsconfig references, never violate):
core ← store ← indexer ← engine ← daemon ← cli; ui talks only to daemon HTTP.
Commands
npm run build— tsc project references + UI (vite)npm run check— lint (biome) + typecheck + all testsnpm run test:unit/npm run test:dogfood— vitest projects (unit aliases vibe-frame-* to sources)npm run version:sync/version:check— root package.json is the only version authority
Conventions
- TypeScript strict, ESM only,
node:import protocol, no default exports. - Biome for lint + format; run
npm run lint:fixbefore committing. - Conventional commits; one coherent module/phase per commit; docs updated in the same commit as behavior.
- Determinism is the product: no wall-clock/randomness in library code paths without injection
(
Clock/IdSourceinterfaces in core); tests must be seed- and time-stable. - Validator precision invariant: every reflexion check has a false-positive corpus under its package tests; a check firing on its corpus is a CI failure.
- Three version domains, never conflated: product semver (root package.json),
.vibeframeschemaVersion (SCHEMA_VERSIONin core), SQLite index schema (PRAGMA user_version, rebuild on mismatch). - Tool output discipline: MCP responses stay far under the 25k-token cap — compact, paginated, cursor-carrying.
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.
- 6d ago First seen · 46 lines · 712 tokens per session scan A 9341da5eb091
vibeframe CLAUDE.md is an instructions file published in the GitHub repository jubayertalha/vibeframe (0 stars, last pushed 10d ago), licensed MIT. It adds 712 tokens to every session, about $0.0036 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-31.
Other instructions, from other repositories
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).
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.
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.
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).
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.