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 rules/daveepope/beanz/beanz-agentgit clone --depth 1 https://github.com/daveepope/beanzWhat 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.01286 | $0.01286 |
| Opus 5 | $0.00643 | $0.00643 |
| Sonnet 5 | $0.00257 | $0.00257 |
| Haiku 4.5 | $0.00129 | $0.00129 |
Grade A, and why
beanz-agent 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 2d 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 — 68 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.
- 2d ago First seen · 68 lines · 1,286 tokens per session scan A 106d65f4128c
beanz-agent is a cursor rule published in the GitHub repository daveepope/beanz (5 stars, last pushed 4d ago), licensed MIT. It adds 1,286 tokens to every session, about $0.0064 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 cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
coolify-ai-docs
Master reference to all Coolify AI documentation in .ai/ directory.
typescript
Changes to these high-fan-out internals can affect every message, delta, element, or rerun. Keep work in them minimal, and benchmark changes with representative stress-test apps.
python_lib
Tips and guidelines specific to the development of the Streamlit Python library, not applicable to scripts and e2e tests.
specs
This directory contains product and tech specs for Streamlit features.