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/kajogo777/bento/agents-mdgit clone --depth 1 https://github.com/kajogo777/bentoWrote 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/kajogo777/bento/agents-md)<a href="https://agentmods.dev/instructions/kajogo777/bento/agents-md"><img src="https://agentmods.dev/badge/instructions/kajogo777/bento/agents-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.04129 | $0.04129 |
| Opus 5 | $0.02065 | $0.02065 |
| Sonnet 5 | $0.00826 | $0.00826 |
| Haiku 4.5 | $0.00413 | $0.00413 |
Grade C, and why
bento AGENTS.md scanned grade C with 1 finding 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 5d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
make clean # rm -rf bin/ dist/ How it starts
The opening of the file, as written. The whole thing — 314 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md - Bento Development Guide
Project Overview
Bento packages AI agent workspace state into portable, layered OCI artifacts. It captures everything git doesn't: agent memory, installed dependencies, build caches, conversation history, and session state. Checkpoints are stored as standard OCI images in any container registry.
Repository: github.com/kajogo777/bento
Language: Go (1.25+)
License: Apache 2.0
Architecture
cmd/bento/main.go → entrypoint, version injection
internal/
cli/ → cobra commands (init, save, open, list, diff, etc.)
config/ → bento.yaml parsing, validation, platform defaults
extension/ → composable extensions (agent, deps, tool detection)
workspace/ → file scanning, layer packing (tar+gzip), .bentoignore
registry/ → OCI store (local image layout + remote push)
manifest/ → OCI manifest/config construction, annotations, DAG
secrets/ → secret scanning (gitleaks), env hydration, providers, scrubbing, backends
hooks/ → lifecycle hook execution (pre_save, post_restore, etc.)
policy/ → garbage collection (retention tiers, blob pruning)
watcher/ → file-system watcher for auto-checkpointing
Key Design Decisions
-
Standard OCI media types - All layers use
application/vnd.oci.image.layer.v1.tar+gzipsodocker pull,COPY --from, and containerd work natively. Layer semantics are carried byorg.opencontainers.image.titleannotations. -
Shared blob store - Local OCI store at
~/.bento/store/uses a shared content-addressed blob pool. Identical layers across workspaces are stored once. -
Composable extensions - Each agent framework, language, and tool gets a small extension that contributes patterns to the right layer. Extensions auto-detect and merge. No monolithic harnesses.
-
Three core layers - deps (rarely changes, large), agent (changes often, small), project (catch-all). Extensions can add more layers (e.g.,
build-cache).
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.
- 5d ago First seen · 314 lines · 4,129 tokens per session scan C 82bf331f9bdf
bento AGENTS.md is an instructions file published in the GitHub repository kajogo777/bento (22 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 4,129 tokens to every session, about $0.0206 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
ecspresso CLAUDE.md
Claude Code instructions for kayac/ecspresso, covering claude.md, project overview, git workflow, build commands and build the binary.
graymatter AGENTS.md
AGENTS.md instructions for angelnicolasc/graymatter, covering agents.md, your tools, when to call which, first calls and identity.
homebutler CLAUDE.md
Claude Code instructions for Higangssh/homebutler, covering homebutler, verify before claiming anything works, writing commits, prs, and comments, no tool attribution and commit subjects.
ephemeral-sandbox CLAUDE.md
Instructions for Ephemeral-AI-Lab/ephemeral-sandbox, covering claude.md, project, engineering practice (required), build & test and sandbox tools.
GoodMemory AGENTS.md
AGENTS.md instructions for hjqcan/GoodMemory, covering repository guidelines, project structure & module organization, build, test, and development commands, coding style & naming conventions and testing guidelines.
claude-tools-mcp CLAUDE.md
Claude Code instructions for mathematic-inc/claude-tools-mcp, covering claude.md, project overview, development commands, building and running tests.