BrewMe: Instructions file for Claude Code

CLAUDE.md

BrewMe CLAUDE.md is an instructions file for Claude Code from xiaojiou176-open/BrewMe. It costs 415 tokens per session, scanned A, original, MIT.

A set of collaboration rules for the BrewMe software repository. It defines which documentation is authoritative, where public information belongs, and how AI agents should edit and test the code.

In plain words
What is it for?
Use it when working on BrewMe to find the right project documentation, preserve the public-facing structure, avoid exposing internal files, and verify meaningful changes.
Why use it?
It reduces confusion when documentation and code differ, and sets safety boundaries for changes to a public project.

Instructions file for Claude Code

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

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

Reuse

Borrowing it

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

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 BrewMe CLAUDE.md

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/xiaojiou176-open/brewme/claude-md"><img src="https://agentmods.dev/badge/instructions/xiaojiou176-open/brewme/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 415 This file is loaded in full into every session.
When invoked 415 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.00415 $0.00415
Opus 5 $0.00208 $0.00208
Sonnet 5 $0.00083 $0.00083
Haiku 4.5 $0.00042 $0.00042

Measured 10d ago against content hash 49c09dbe7977, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-10, from the pricing page.

Security

Grade A, and why

BrewMe 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 10d 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 · 52 lines

What it actually says

Repository Collaboration Contract

This repository is a public, source-first engineering project. The public surface MUST stay thin, truthful, and easy to navigate.

Core Rules

  1. README.md is the front door.
  2. docs/start-here.md is the quickstart and operator entrypoint.
  3. docs/architecture.md is the system map.
  4. docs/testing.md is the testing and CI contract.
  5. Runtime, cache, logs, and agent workspaces MUST stay out of the tracked public surface.
  6. Root documentation MUST stay concise and public-facing. Internal audit logs, rehearsal notes, and execution ledgers MUST NOT return.
  7. AI agents MUST read before editing, prefer surgical changes, and verify meaningful behavior with real commands.
  8. Commits, branch rewrites, and force-pushes are allowed only when explicitly authorized by the human maintainer.

Source Of Truth

Priority order:

  1. docs/start-here.md
  2. docs/architecture.md
  3. docs/testing.md
  4. README.md

If docs and code drift, update the lower-priority surface to match the higher-priority truth.

Public Navigation

  • README.md
  • docs/start-here.md
  • docs/architecture.md
  • docs/testing.md
  • CONTRIBUTING.md
  • SECURITY.md
  • SUPPORT.md

Safety Boundaries

  • Never commit secrets, private credentials, or customer data.
  • Never track .agents/, .agent/, .codex/, .claude/, .runtime-cache/, logs/, log/, or *.log.
  • Never treat generated runtime reports as durable documentation.
  • Never describe the repository as fully verified for external distribution unless the live remote workflows prove it for the current main head.

Delivery Format

Execution updates SHOULD include:

  1. Changed files
  2. Executed commands
  3. Results
  4. Risks and follow-up
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. 10d ago First seen · 52 lines · 415 tokens per session scan A 49c09dbe7977

Subscribe to this mod's changes

BrewMe CLAUDE.md is an instructions file published in the GitHub repository xiaojiou176-open/BrewMe (2 stars, last pushed 3mo ago), licensed MIT. It adds 415 tokens to every session, about $0.0021 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.

Related

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.

vercel/next.js · 7,296 tokens

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.

openai/codex · 5,153 tokens

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 · 6,785 tokens

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.

github/spec-kit · 7,104 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, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 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,469 tokens