beans CLAUDE.md

Project instructions for Beans, an issue tracker whose work items are Markdown files stored in a repository.

In plain words
What is it for?
Working on the Beans CLI, terminal interface, or web interface, including its GraphQL server, agent chats, worktrees, file diffs, and terminal sessions.
Why use it?
They give contributors consistent rules for the project’s interfaces, commits, pull requests, and development structure.

Instructions file

Install

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.

agentmods
npx agentmods add instructions/hmans/beans/claude-md
Clone the repo
git clone --depth 1 https://github.com/hmans/beans
Per session 1,364 This file is loaded in full into every session.
When invoked 1,364 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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.

ModelPer sessionOnce invoked
Fable 5 $0.01364 $0.01364
Opus 5 $0.00682 $0.00682
Sonnet 5 $0.00273 $0.00273
Haiku 4.5 $0.00136 $0.00136

Measured 2d ago against content hash 35d85f148d22, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

beans 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 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.

CLAUDE.md · 91 lines

How it starts

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

What we're building

Beans is an agentic-first issue tracker. Issues ("beans") live as markdown files in a .beans/ directory inside a project repo. The system has three interfaces:

  • CLI (beans binary) — create, list, update, and query beans from the terminal
  • Terminal TUI — Bubbletea-based interactive interface
  • Beans UI (beans serve) — SvelteKit SPA served by an embedded Go HTTP server, communicating via GraphQL (queries, mutations, subscriptions over WebSocket)

The Beans UI is the primary development focus. It includes a backlog board, per-bean agent chat (spawning Claude Code processes), git worktree management, file change diffs, and terminal sessions.

Commits

  • Use conventional commit messages ("feat", "fix", "chore", etc.) when making commits.
  • Include the relevant bean ID(s) in the commit message (please follow conventional commit conventions, e.g. Refs: bean-xxxx).
  • Mark commits as "breaking" using the ! notation when applicable (e.g., feat!: ...).
  • When making commits, provide a meaningful commit message. The description should be a concise bullet point list of changes made.

Pull Requests

  • When we're working in a PR branch, make separate commits, and update the PR description to reflect the changes made.
  • Include the relevant bean ID(s) in the PR title (please follow conventional commit conventions, e.g. Refs: bean-xxxx).

Project Structure

Key packages:

  • pkg/bean/ — Bean data model, parsing, sorting, validation (no I/O)
  • pkg/beancore/ — Core engine: disk I/O, file watching, search indexing, worktree watching
  • internal/graph/ — GraphQL schema and resolvers (the API layer for both Beans UI and CLI)
  • internal/agent/ — Agent session manager: spawns Claude Code processes, parses JSONL output, pub/sub for real-time updates
  • internal/worktree/ — Git worktree lifecycle management
  • internal/terminal/ — PTY session management for embedded terminals
  • internal/commands/ — CLI command implementations (Cobra)
  • frontend/ — SvelteKit SPA (embedded into the Go binary via //go:embed)

Read the full file on GitHub · 91 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.

  1. 2d ago First seen · 91 lines · 1,364 tokens per session scan A 35d85f148d22

Subscribe to this mod's changes

beans CLAUDE.md is an instructions file published in the GitHub repository hmans/beans (911 stars, last pushed 4mo ago), licensed Apache-2.0. It adds 1,364 tokens to every session, about $0.0068 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.