Borrowing it
Nothing to install: this file belongs to bluebear-io/angry-bear. 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/bluebear-io/angry-bear/main/CLAUDE.mdgit clone --depth 1 https://github.com/bluebear-io/angry-bearWrote 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/bluebear-io/angry-bear/claude-md)<a href="https://agentmods.dev/instructions/bluebear-io/angry-bear/claude-md"><img src="https://agentmods.dev/badge/instructions/bluebear-io/angry-bear/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.00903 | $0.00903 |
| Opus 5 | $0.00451 | $0.00451 |
| Sonnet 5 | $0.00181 | $0.00181 |
| Haiku 4.5 | $0.00090 | $0.00090 |
Grade A, and why
angry-bear 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 6d 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 — 85 lines — stays where its author put it; the contents beside it link to each section on GitHub.
angry-bear — Agent Guidelines
Overview
angry-bear enforces skill-loading requirements for AI coding agents. Before modifying any code, read docs/HIGHLEVEL.md to understand how enforcement, state management, and the adapter architecture work.
Repository Structure
internal/
adapter/ Agent-specific logic (Claude, Cursor). ALL agent knowledge lives here.
cli/ Cobra commands (hook, init, status, clean, doctor, version)
engine/ Core enforcement (ShouldBlock, config loading, glob matching) — agent-agnostic
state/ File-based session state with advisory locks and atomic writes
scanner/ Skill discovery from configured paths
tui/ Charmbracelet TUI (dashboard, rule editor, tree picker, settings)
cmd/angry-bear/ Entry point — wires dependencies, nothing else
Architecture Rules
-
All agent-specific logic lives in adapters. The engine, TUI, CLI, and state packages know nothing about Claude, Cursor, or any specific agent. If you write
if agent == "claude"outsideinternal/adapter/, you're doing it wrong. -
The HookAdapter interface is the extension point. See
internal/adapter/adapter.go. New agents implement this interface and register inregistry.go. Everything else works automatically. -
No global mutable state. Adapters receive configuration via struct fields. No
init()functions. No package-level mutable variables. -
Shared TUI components. All scrollable lists use
ScrollViewfrominternal/tui/scroll.go. No ad-hoc scroll logic.ToolOptions,AgentOptions,DefaultIgnoreSetlive ininternal/tui/constants.go.
Code Standards
This project follows strict Go coding standards:
- gofmt + golangci-lint must pass with zero issues
- 80% minimum test coverage enforced by CI — every package must meet this individually
- Table-driven tests for functions with multiple input patterns
- t.TempDir() for all filesystem tests — never write to real paths
- Never swallow errors — wrap with context or log them
- No shorthand if — separate assignment from condition
- Octal format — use
0o755not0755
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.
- 6d ago First seen · 85 lines · 903 tokens per session scan A d7594053bce4
angry-bear CLAUDE.md is an instructions file published in the GitHub repository bluebear-io/angry-bear (17 stars, last pushed today), licensed MIT. It adds 903 tokens to every session, about $0.0045 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-30.
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.
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).
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).
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.
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.