Borrowing it
Nothing to install: this file belongs to sawzhang/bruin. 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/sawzhang/bruin/master/CLAUDE.mdgit clone --depth 1 https://github.com/sawzhang/bruinWrote 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/sawzhang/bruin/claude-md)<a href="https://agentmods.dev/instructions/sawzhang/bruin/claude-md"><img src="https://agentmods.dev/badge/instructions/sawzhang/bruin/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.01904 | $0.01904 |
| Opus 5 | $0.00952 | $0.00952 |
| Sonnet 5 | $0.00381 | $0.00381 |
| Haiku 4.5 | $0.00190 | $0.00190 |
Grade A, and why
bruin 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 7d 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 — 118 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.
Commands
# Development
npm run tauri dev # Start app (Vite + Tauri hot reload)
npm run tauri build # Production build → .dmg in src-tauri/target/release/bundle/
# Frontend tests
npm test # Run Vitest once
npm run test:watch # Watch mode
# Rust checks
cd src-tauri && cargo check # Type check Rust
cd src-tauri && cargo clippy # Lint Rust
# MCP server (built into the app binary)
/Applications/Bruin.app/Contents/MacOS/bruin --mcp # Start MCP server (stdio)
/Applications/Bruin.app/Contents/MacOS/bruin --install-skill # Install Claude Code skill
/Applications/Bruin.app/Contents/MacOS/bruin --write-config # Write Claude Code MCP config
Architecture
Bruin is a Tauri 2 desktop app: Rust backend + React 19 frontend with a native MCP server built into the app binary.
Data flow
AI Agent ──MCP (stdio)──► Bruin Binary (Rust) ──► SQLite ◄──IPC──► React Frontend
│
iCloud Sync
(bidirectional .md files)
The MCP server runs as the same binary with --mcp flag: bruin --mcp. It accesses SQLite directly — no Node.js required. The GUI app and MCP server share the same database at ~/Library/Application Support/com.bruin.notes/bruin.db.
Frontend (src/)
- IPC bridge:
src/lib/tauri.ts— every Tauriinvoke()call is wrapped here. Stores never callinvoke()directly. - State: Zustand stores in
src/stores/—noteStore,workspaceStore,graphStore,tagStore,activityStore,uiStore. Each store calls functions fromtauri.tsand manages its own slice. - Editor: TipTap-based rich markdown editor in
src/components/editor/. - Graph: D3 force-directed visualization in
src/components/graph/. - Themes: 6 themes defined in
src/lib/themes.ts, applied via CSS variables with Tailwind'sbear.*namespace.
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.
- 7d ago First seen · 118 lines · 1,904 tokens per session scan A 408ac0bb874c
bruin CLAUDE.md is an instructions file published in the GitHub repository sawzhang/bruin (2 stars, last pushed 4mo ago), licensed MIT. It adds 1,904 tokens to every session, about $0.0095 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.