Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/daveepope/beanz/claude-mdgit clone --depth 1 https://github.com/daveepope/beanzWrote 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/daveepope/beanz/claude-md)<a href="https://agentmods.dev/instructions/daveepope/beanz/claude-md"><img src="https://agentmods.dev/badge/instructions/daveepope/beanz/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 | $0.01259 | $0.01259 |
| Opus 5 | $0.00629 | $0.00629 |
| Sonnet 5 | $0.00252 | $0.00252 |
| Haiku 4.5 | $0.00126 | $0.00126 |
Grade A, and why
beanz 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 4d 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.
This is a copy
100% identical to beanz AGENTS.md — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
beanz — agent instructions
General programming workflows
- beanz is a Rust-only Cargo project (cognitive debt scoring for AI coding sessions). Use idiomatic Rust unless stated otherwise.
- No drive-by refactors or unrelated files; no new markdown/docs unless the user asks (e.g. READMEs).
- Use
cargo checkfor fast feedback during iteration; runcargo test(andcargo build --releasewhen relevant) before considering work done. - Always report to the developer if you are adding any new third-party crates.
- Never stray away from the plan set out by the developer.
- Function as an informative AI coding agent to assist the developer with features, bugs, test coverage, and architecture.
- Stay within the bounds of the task set out to you.
- If you are not confident in your answers, say so — honesty is critical.
- Do not commit unless the developer explicitly asks. Ask first before creating a commit; leave changes for the developer to review and commit when they have not asked.
AI communication
- Keep replies concise and consistent in tone and structure.
- Be clear; ask direct questions when something is ambiguous. Do not waffle, hedge with filler, or pad with generic advice.
- If you are not sure of an answer, say so plainly and work with the developer to close the knowledge gap (what you need checked, what options depend on unknowns, what to read or run next).
Naming conventions (strict)
- Do not use the words mock, manager, integration test, utility, helper, or sink as substrings in beanz-authored identifiers or API symbols, or in string literals you choose (e.g. not
SessionManager,build_helper). Applies to types, functions, methods, fields, locals, modules, and exposed config keys. Prefer neutral names such assetup_*,build_*,with_*,prepare_*. - This applies to the entire codebase, not only
pubitems.
Public API and abstractions
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.
- 4d ago First seen · 63 lines · 1,259 tokens per session scan A 8124671a02eb
beanz CLAUDE.md is an instructions file published in the GitHub repository daveepope/beanz (5 stars, last pushed 6d ago), licensed MIT. It adds 1,259 tokens to every session, about $0.0063 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to beanz AGENTS.md, differing in 0 lines, and is treated as a copy.
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).
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.
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.