vibe-workspace: Instructions file for Claude Code

CLAUDE.md

vibe-workspace CLAUDE.md is an instructions file for Claude Code from toolprint/vibe-workspace. It costs 1,570 tokens per session, scanned A, original, MIT.

Repository instructions for developing, testing, formatting, packaging, and releasing the toolprint/vibe-workspace project.

In plain words
What is it for?
They cover debug and release builds, running tests, linting and formatting, cross-platform binaries, artifact checks, GitHub releases, and package publishing.
Why use it?
They give coding agents and developers the project’s expected commands and validation steps.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md. Also seen: mentions CLAUDE.md; mentions Claude Code.

This is toolprint/vibe-workspace's own configuration. It tells Claude Code how to work on vibe-workspace 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-workspace configures →

Reuse

Borrowing it

Nothing to install: this file belongs to toolprint/vibe-workspace. 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/toolprint/vibe-workspace/main/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/toolprint/vibe-workspace

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.

agentmods badge for vibe-workspace CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/toolprint/vibe-workspace/claude-md/github.svg)](https://agentmods.dev/instructions/toolprint/vibe-workspace/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/toolprint/vibe-workspace/claude-md"><img src="https://agentmods.dev/badge/instructions/toolprint/vibe-workspace/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.

agentmods 80×15 button for vibe-workspace CLAUDE.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/toolprint/vibe-workspace/claude-md"><img src="https://agentmods.dev/badge/instructions/toolprint/vibe-workspace/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,570 This file is loaded in full into every session.
When invoked 1,570 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.01570 $0.01570
Opus 5.5 $0.00628 $0.00628
Sonnet 5.5 $0.00314 $0.00314
Haiku 4.5 $0.00157 $0.00157

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

Security

Grade A, and why

vibe-workspace 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 · 146 lines

How it starts

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

CLAUDE.md

This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.

Core Commands

Development Workflow

# Build and development
just build                    # Debug build
just build-release           # Release build with optimization
just install                 # Install from zigbuild release artifacts
just run -- [args]          # Run with arguments (e.g., just run -- --help)

# Testing and validation
just test                    # Run all tests
just test-mcp               # Run MCP-specific tests
just pre-commit             # Full validation (check, format, clippy, tests)

# Code quality
just check                  # Cargo check (fast compilation check)
just fmt                    # Format code
just clippy                 # Run clippy linter
just clean                  # Clean build artifacts

Cross-Platform Release

# Build all platform binaries
just zigbuild-release       # Build for Linux x86_64, macOS x86_64/ARM64/Universal2

# Complete release workflow
just release-all            # Full release: validation → GitHub → cargo publish
just validate-artifacts     # Validate built binaries
just create-github-release  # Create GitHub release + upload artifacts
just cargo-publish          # Publish to crates.io

MCP Development

# Interactive MCP testing
just mcp-inspector          # Launch Inspector UI for visual testing
just mcp-inspector-cli      # CLI mode testing
just mcp-validate           # Validate MCP-CLI consistency

Architecture Overview

Core Entry Point

  • src/main.rs - CLI argument parsing using Clap, command routing, and application orchestration
  • Binary name: vibe (defined in Cargo.toml)
  • Uses async runtime (Tokio) with full feature set

Module Structure

Workspace Management (src/workspace/)
  • manager.rs - Core WorkspaceManager struct that coordinates all operations
  • config.rs - Configuration structures for repositories, apps, and workspace settings
  • constants.rs - Paths and configuration directories (~/.toolprint/vibe-workspace/)
  • discovery.rs - Repository discovery and scanning logic
  • operations.rs - Git operations (status, sync, execute commands)
  • templates.rs - Template management for app integrations
  • install.rs - Installation and setup workflows

Read the full file on GitHub · 146 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. 2mo ago First seen · 146 lines · 1,570 tokens per session scan A 4c19fc593135

Subscribe to this mod's changes

vibe-workspace CLAUDE.md is an instructions file published in the GitHub repository toolprint/vibe-workspace (9 stars, last pushed 1y ago), licensed MIT. It adds 1,570 tokens to every session, about $0.0063 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-31.

Related

Other instructions, from other repositories

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 · 9,715 tokens

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,461 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, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 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,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,750 tokens

deno copilot-instructions.md

Copilot instructions for denoland/deno, covering deno development guide for github copilot, network access, high level overview, key directories and key files to understand first.

denoland/deno · 3,077 tokens