What is brometal CLAUDE.md?

A project guide for the BroMetal codebase that sets repository-specific development rules. It covers where to edit, how to verify changes, and how to keep the changelog current.

Use it when modifying BroMetal packages to follow the required file scope, update the Unreleased changelog, and run the expected checks.

It prevents common maintenance mistakes, such as changing the wrong files or forgetting to record updates before release.

How ericdrowell/brometal configures Claude Code

Reuse

Borrowing it

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

Clone the repo

git clone --depth 1 https://github.com/ericdrowell/brometal

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/ericdrowell/brometal/claude-md/github.svg)](https://agentmods.dev/instructions/ericdrowell/brometal/claude-md)

Your own site

<a href="https://agentmods.dev/instructions/ericdrowell/brometal/claude-md"><img src="https://agentmods.dev/badge/instructions/ericdrowell/brometal/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/ericdrowell/brometal/claude-md"><img src="https://agentmods.dev/badge/instructions/ericdrowell/brometal/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 1,099 This file is loaded in full into every session.

When invoked 1,099 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.01099	$0.01099
Opus 5.5	$0.00440	$0.00440
Sonnet 5.5	$0.00220	$0.00220
Haiku 4.5	$0.00110	$0.00110

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

Security

Grade A, and why

brometal 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 · 112 lines

How it starts

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

Working on BroMetal

Instructions for Claude working on this repository. If you are writing an app that uses BroMetal, read packages/brometal/AGENTS.md instead.

Start with AGENTS.md at this root — it covers the layout, the commands, and the failure modes that have bitten before. This file adds the things that are easy to skip.

Always update the changelog

Any change under packages/brometal/ gets a CHANGELOG.md entry in the same change. Not at release time, not "later" — now, while you still remember why.

The log currently jumps from ## Unreleased straight to 0.7.0. Versions 0.8 through 0.12 shipped with no entries at all, because writing them was a separate step that got skipped. That is the failure this rule exists to prevent.

Add to the ## Unreleased section at the top. Never write a version number — the version is not chosen until npm run release runs, and the release script promotes ## Unreleased to ## <version> (<date>) and opens a fresh empty one.

There are exactly three sections, and they always appear in this order:

### Added — new API surface
### Improved — existing behaviour made better, including breaking changes
### Fixed — a bug that shipped

There is no Changed. Every change is an addition, an improvement, or a fix.

Never create a second section with the same name. Add your bullet to the existing ### Added / ### Improved / ### Fixed, creating it only if absent. Appending a fresh ### Added at the bottom of the section is the easy mistake — it renders as two separate lists and the reader cannot tell why.

Mark anything source-incompatible Breaking, in Improved, and say what to do instead.

Changes that do not need an entry: website content, README edits, tests, comments, and internal refactors with no behavioural difference.

Only edit the root file

/CHANGELOG.md is the source of truth. Two things derive from it:

The website (/changelog) parses the root file at build time. No copy exists, so it cannot drift.
packages/brometal/CHANGELOG.md is a copy written by npm run sync:examples, so the file is readable from node_modules. Never edit it — the next sync overwrites it silently. It is committed rather than gitignored because npm falls back to .gitignore in the absence of an .npmignore, and an ignored file would not ship.

Read the full file on GitHub · 112 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 · 112 lines · 1,099 tokens per session scan A 9364806d90c5

Subscribe to this mod's changes

brometal CLAUDE.md is an instructions file published in the GitHub repository ericdrowell/brometal (107 stars, last pushed 1mo ago), licensed MIT. It adds 1,099 tokens to every session, about $0.0044 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.

TypeScript compiler shaders webgpu

brometal CLAUDE.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
brometal CLAUDE.mdericdrowell/brometal	Instructions file	107	1mo ago	MIT	A	1,099	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	yesterday	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

brometal: Instructions file for Claude Code