berd: Instructions file for Codex

AGENTS.md

berd AGENTS.md is an instructions file for Codex, OpenCode from block/berd. It costs 1,586 tokens per session, scanned A, original, Apache-2.0.

A set of project instructions for developers and coding agents working on Berd, a desktop application built with Tauri and React.

In plain words
What is it for?
Use it when modifying Berd’s interface, desktop shell, agent-session system, bundled assets, or managed Goose and ACP components.
Why use it?
It explains the project’s folder structure, required components, pinned dependencies, and architectural rules before changes are made.

Instructions file for CodexOpenCode ✓ vendor

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions AGENTS.md.

This is block/berd's own configuration. It tells Codex and OpenCode how to work on berd itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything berd configures →

View source ↗ block/berd
About the project

Berd is an open-source desktop application for working with AI agents through a graphical interface. It is intended for people who want to use different AI models and an integrated Goose backend from a desktop app. The catalogue entries add agent skills, agents, and instructions for working within Berd.

block/berd · 1,007 stars · on GitHub

Reuse

Borrowing it

Nothing to install: this file belongs to block/berd. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/block/berd/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/block/berd

Made for: Codex, OpenCode.

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

agentmods badge for berd AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/block/berd/agents-md/github.svg)](https://agentmods.dev/instructions/block/berd/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/block/berd/agents-md"><img src="https://agentmods.dev/badge/instructions/block/berd/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for berd AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/block/berd/agents-md"><img src="https://agentmods.dev/badge/instructions/block/berd/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,586 This file is loaded in full into every session.
When invoked 1,586 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.1 $0.01586 $0.01586
Opus 5.5 $0.00634 $0.00634
Sonnet 5.5 $0.00317 $0.00317
Haiku 4.5 $0.00159 $0.00159

Measured 12d ago against content hash 59fdf52b4ef0, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

berd 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 12d 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 · 140 lines

How it starts

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

AGENTS.md

Guidelines for agents working on Berd.

Berd is a standalone Tauri 2 + React 19 desktop. ACP is the main interface we use for the actual agent loop - creating and running sessions, finding available models, and setting configuration. When available, we work over ACP methods, but the UI can handle operations that are not yet in ACP or are client specific.

Layout

  • src/ — React UI/features/shared code
  • src-tauri/ — Tauri shell that starts or resolves goose serve
  • sdk/ — vendored @aaif/goose-sdk package and generated ACP types
  • distro/ — bundled app defaults and packaged distribution assets
  • goose-backend.lock.json — pinned upstream Goose backend used by dev and bundles
  • acp-tools.lock.json — release-controlled package.json + package-lock.json the managed ACP bridges are installed from with npm ci
  • scripts/ensure-local-goose.sh — managed local Goose checkout for dev
  • scripts/prepare-goose-sidecar.sh — stages the pinned or explicit Goose binary for Tauri bundling
  • scripts/update-goose-backend-lock.sh — resolves and records a new Goose backend pin
  • scripts/update-acp-tools-lock.mjs — resolves and records a new managed ACP bridge pin
  • src/features/berdctl/ — berdctl command registry
  • src-tauri/plugins/berdctl/ — berdctl broker
  • src-tauri/crates/berdctl/ — bundled berdctl CLI
  • distro/skills/berd-help/references/berdctl.md — berdctl guidance agents read from the bundled berd-help skill

Architectural laws

LAWS/ defines required product and user experience behavior. Before planning, implementing, or reviewing behavior changes, read LAWS/README.md and every law file relevant to the affected behavior. Laws take correctness precedence over the current code and tests; when they disagree, change the implementation and tests or explicitly propose a product-approved law change.

Startup assets

Startup artifact media is resolved by the Tauri backend and returned as local cache paths. Renderer code should use getArtifacts() or selectProjectPreviewArtifacts() from src/shared/api/artifacts.ts, then pass paths through convertFileSrc(..., "asset") before rendering media. Do not vendor startup media, fetch catalogs in the renderer, or construct CDN URLs in UI code.

Read the full file on GitHub · 140 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. 12d ago Changed · +6 lines · +48 tokens per session 59fdf52b4ef0
  2. 1mo ago First seen · 134 lines · 1,538 tokens per session scan A b7530938cc4f

Subscribe to this mod's changes

berd AGENTS.md is an instructions file published in the GitHub repository block/berd (1,007 stars, last pushed 2d ago), licensed Apache-2.0. It adds 1,586 tokens to every session, about $0.0063 per session on Opus 5.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.

Related

Other instructions, from other repositories

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 · 9,715 tokens

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,581 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).

microsoft/vscode · 5,262 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,680 tokens

vscode copilot-instructions.md

Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).

microsoft/vscode · 2,731 tokens

deepseek-harness AGENTS.md

AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.

deepseek-ai/deepseek-harness · 4,261 tokens