What is vibeusage CLAUDE.md?

A project guidance file for Claude Code, an AI assistant that helps edit software. It describes when to use OpenSpec, a workflow for proposing and tracking significant changes.

Use it to check project conventions, list active specifications, create change proposals, validate them, and archive completed proposals.

It helps the assistant follow the project's existing development process instead of making major changes without a written proposal. It also distinguishes feature work from smaller fixes.

How victorGPT/vibeusage configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to victorGPT/vibeusage. 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/victorGPT/vibeusage/main/CLAUDE.md

Clone the repo

git clone --depth 1 https://github.com/victorGPT/vibeusage

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/victorgpt/vibeusage/claude-md/github.svg)](https://agentmods.dev/instructions/victorgpt/vibeusage/claude-md)

Your own site

<a href="https://agentmods.dev/instructions/victorgpt/vibeusage/claude-md"><img src="https://agentmods.dev/badge/instructions/victorgpt/vibeusage/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/victorgpt/vibeusage/claude-md"><img src="https://agentmods.dev/badge/instructions/victorgpt/vibeusage/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 497 This file is loaded in full into every session.

When invoked 497 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.

Model	Per session	Once invoked
Fable 5.1	$0.00497	$0.00497
Opus 5.5	$0.00199	$0.00199
Sonnet 5.5	$0.00099	$0.00099
Haiku 4.5	$0.00050	$0.00050

Measured 2mo ago against content hash 6918918fe549, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

vibeusage 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 2mo 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.

CLAUDE.md · 74 lines

How it starts

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

Project Guidelines for Claude Code

OpenSpec Workflow

This project uses OpenSpec for spec-driven development. Before making significant changes:

Read openspec/project.md for project conventions
Check openspec/AGENTS.md for the full OpenSpec workflow
Run openspec list to see active changes
Run openspec list --specs to see existing specifications

When to Create a Proposal

Create a proposal (openspec/changes/<id>/) for:

New features or capabilities
Breaking changes (API, schema)
Architecture or pattern changes
Security-related changes

Skip proposals for:

Bug fixes (restore intended behavior)
Typos, formatting, comments
Dependency updates (non-breaking)

OpenSpec Commands

openspec list                     # List active changes
openspec list --specs             # List specifications
openspec show <item>              # View change or spec details
openspec validate <id> --strict   # Validate a change proposal
openspec archive <id> --yes       # Archive after deployment

Proposal Structure

openspec/changes/<change-id>/
├── proposal.md     # Why and what
├── tasks.md        # Implementation checklist
├── design.md       # Technical decisions (optional)
└── specs/
    └── <capability>/
        └── spec.md # ADDED/MODIFIED/REMOVED requirements

Project Structure

src/ - CLI source code (Node.js, CommonJS)
bin/ - CLI entry points
dashboard/ - React dashboard (Vite)
insforge-src/ - Backend Edge Functions source
insforge-functions/ - Built backend functions (generated)
openspec/ - Specifications and change proposals

Key Commands

npm test                          # Run tests
npm run build:insforge            # Build backend functions
npm run dashboard:dev             # Start dashboard dev server
npm run validate:copy             # Validate copy registry

Conventions

Platform: macOS-first
All user-facing text managed in dashboard/src/content/copy.csv
Token data only - never store or upload conversation content
Use UTC for all timestamps
Half-hour buckets for aggregation

Read the full file on GitHub · 74 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.

2mo ago First seen · 74 lines · 497 tokens per session scan A 6918918fe549

Subscribe to this mod's changes

vibeusage CLAUDE.md is an instructions file published in the GitHub repository victorGPT/vibeusage (130 stars, last pushed 3mo ago), licensed MIT. It adds 497 tokens to every session, about $0.0020 per session on Opus 5.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.

Planning

vibeusage CLAUDE.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
vibeusage CLAUDE.mdvictorGPT/vibeusage	Instructions file	130	3mo ago	MIT	A	497	Claude Code
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	today	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

vibeusage: Instructions file for Claude Code