What is bdh AGENTS.md?

Project instructions for BeadHub, a tool for coordinating coding agents and tracking shared issues.

They guide session startup, finding available work, sending mail, checking team status, and using BeadHub instead of its underlying issue tool directly.

They help an agent follow the team’s current policy, notice messages from other agents, and use the project’s coordination commands correctly.

bdh AGENTS.md — Instructions file by beadhub

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/beadhub/bdh/agents-md

Clone the repo

git clone --depth 1 https://github.com/beadhub/bdh

Made for: Codex, OpenCode.

Per session 801 This file is loaded in full into every session.

When invoked 801 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.

Model	Per session	Once invoked
Fable 5	$0.00801	$0.00801
Opus 5	$0.00400	$0.00400
Sonnet 5	$0.00160	$0.00160
Haiku 4.5	$0.00080	$0.00080

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

Security

Grade A, and why

bdh AGENTS.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.

AGENTS.md · 76 lines

How it starts

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

Project Context

See docs/sot.md for what this repo is, how it fits in the ecosystem, and key patterns.

BeadHub Coordination Rules

This project uses bdh for multi-agent coordination and issue tracking, bdh is a wrapper on top of bd (beads). Commands starting with : like bdh :status are managed by bdh. Other commands are sent to bd.

You are expected to work and coordinate with a team of agents. ALWAYS prioritize the team vs your particular task.

You will see notifications telling you that other agents have written mails or chat messages, or are waiting for you. NEVER ignore notifications. It is rude towards your fellow agents. Do not be rude.

Your goal is for the team to succeed in the shared project.

The active project policy as well as the expected behaviour associated to your role is shown via bdh :policy.

Start Here (Every Session)

bdh :policy    # READ CAREFULLY and follow diligently
bdh :status    # who am I? (alias/workspace/role) + team status
bdh ready      # find unblocked work

Use bdh :help for bdh-specific help.

Rules

Always use bdh (not bd) so work is coordinated
Default to mail (bdh :aweb mail list|open|send) for coordination; use chat (bdh :aweb chat pending|open|send-and-wait|send-and-leave|history|extend-wait) when you need a conversation with another agent.
Respond immediately to WAITING notifications — someone is blocked.
Notifications are for YOU, the agent, not for the human.
Don't overwrite the work of other agents without coordinating first.
ALWAYS check what other agents are working on with bdh :status which will tell you which beads they have claimed and what files they are working on (reservations).
bdh derives your identity from the .beadhub file in the current worktree. If you run it from another directory you will be impersonating another agent, do not do that.
Prioritize good communication — your goal is for the team to succeed

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

2d ago First seen · 76 lines · 801 tokens per session scan A 16198808a495

Subscribe to this mod's changes

bdh AGENTS.md is an instructions file published in the GitHub repository beadhub/bdh (5 stars, last pushed 9d ago), licensed MIT. It adds 801 tokens to every session, about $0.0040 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.

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.

github/spec-kit · 7,104 tokens

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.

openai/codex · 5,182 tokens

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

microsoft/vscode · 6,785 tokens

bdh AGENTS.md