agentmods.dev

beads CLAUDE.md

A short entry-point file that tells Claude Code which Beads instruction files to read first. Beads is a Dolt-backed issue tracker, and Dolt is a version-controlled database used here for issue data.

In plain words
What is it for?
Use it as the starting point for Claude Code work in Beads, especially before tracked work, builds, tests, or issue-data synchronization.
Why use it?
It gives Claude Code the current source of project rules without duplicating details that can become outdated. It also points agents to the correct workflow and synchronization commands.

Instructions file

27k +29 yesterday A scan 281 tokens original MIT
View the source file gastownhall/beads
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/gastownhall/beads/claude-md
Clone the repo
git clone --depth 1 https://github.com/gastownhall/beads
Per session 281 This file is loaded in full into every session.
When invoked 281 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.00281 $0.00281
Opus 5 $0.00140 $0.00140
Sonnet 5 $0.00056 $0.00056
Haiku 4.5 $0.00028 $0.00028

Measured yesterday against content hash 6e6762359098, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

beads 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 yesterday.

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 · 24 lines

What it actually says

Claude Code Entry Point for Beads

This file is intentionally short. Do not copy workflow, build, storage, or UI rules here; those details drift quickly when repeated across agent entrypoints.

Read First

Current Ground Rules

  • Run bd prime before doing tracked work.
  • Follow go.mod and AGENT_INSTRUCTIONS.md for build and test commands; do not hard-code toolchain versions here.
  • Beads uses Dolt as the issue database. Use bd dolt push / bd dolt pull for issue data sync; do not use export/import as a routine git workflow.
  • The CLI Visual Design System lives in AGENT_INSTRUCTIONS.md.
  • If this file conflicts with a linked source, trust the linked source and fix this file by removing the duplicate.
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. yesterday First seen · 24 lines · 281 tokens per session scan A 6e6762359098

Subscribe to this mod's changes

beads CLAUDE.md is an instructions file published in the GitHub repository gastownhall/beads (26,754 stars, last pushed yesterday), licensed MIT. It adds 281 tokens to every session, about $0.0014 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.

DatabasesProject managementTestingagentsclaude-codecoding
Related

Other instructions, from other repositories

yaks AGENTS.md

Instructions for mattwynne/yaks, covering architecture, testing layers, mutation testing, cli design philosophy and development workflow.

mattwynne/yaks · 1,106 tokens

lineark CLAUDE.md

Instructions for flipbit03/lineark, covering claude.md — lineark, what is this, workspace layout, key commands and writing online tests: the three pillars.

flipbit03/lineark · 3,334 tokens

blz AGENTS.md

Instructions for outfitter-dev/blz, covering blz repository instructions for ai agents, important, working memory, use blz and 🚀 quick start for agents.

outfitter-dev/blz · 1,615 tokens

moo-tasks AGENTS.md

Instructions for dizlexic/moo-tasks, covering agents.md, 1. what is the moo tasks board?, 2. connecting your agent, 3. available mcp tools and 4. recommended workflow for agents.

dizlexic/moo-tasks · 3,550 tokens

skill-harness AGENTS.md

Instructions for 45ck/skill-harness, covering skill harness, beads issue tracker, quick reference, rules and session completion.

45ck/skill-harness · 1,545 tokens

agentor CLAUDE.md

Instructions for lonetis/agentor, covering agent orchestrator (agentor), architecture, detailed documentation, tech stack and dev commands.

lonetis/agentor · 4,026 tokens