braynee: Instructions file for Codex

AGENTS.md

braynee AGENTS.md is an instructions file for Codex, OpenCode from hamchowderr/braynee. It costs 1,197 tokens per session, scanned C, a copy of awesome-spain AGENTS.md, MIT.

Project instructions for coding agents working on a repository that uses bd, a command-line issue tracker called Beads.

In plain words
What is it for?
Use them when choosing available issues, claiming or closing work, pushing issue data, or running file operations non-interactively.
Why use it?
They give agents the project’s workflow and prevent shell commands from stopping for confirmation prompts.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: reads .claude/ paths; names the TodoWrite tool.

This is hamchowderr/braynee's own configuration. It tells Codex and OpenCode how to work on braynee 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 braynee configures →

Reuse

Borrowing it

Nothing to install: this file belongs to hamchowderr/braynee. 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/hamchowderr/braynee/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/hamchowderr/braynee

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 braynee AGENTS.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/hamchowderr/braynee/agents-md/github.svg)](https://agentmods.dev/instructions/hamchowderr/braynee/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/hamchowderr/braynee/agents-md"><img src="https://agentmods.dev/badge/instructions/hamchowderr/braynee/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 braynee AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/hamchowderr/braynee/agents-md"><img src="https://agentmods.dev/badge/instructions/hamchowderr/braynee/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,197 This file is loaded in full into every session.
When invoked 1,197 The same file — it is already loaded in full.
Security scan C 2 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 75% copy Near-identical to another mod 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.01197 $0.01197
Opus 5.5 $0.00479 $0.00479
Sonnet 5.5 $0.00239 $0.00239
Haiku 4.5 $0.00120 $0.00120

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

Security

Grade C, and why

braynee AGENTS.md scanned grade C with 2 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 4d 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.

rm -rf directory # NOT: rm -r directory

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

with `curl -s http://127.0.0.1:7717`. File mode needs only a hard reload.
Origin

This is a copy

75% identical to awesome-spain AGENTS.md — 77 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

AGENTS.md · 111 lines

How it starts

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

Agent Instructions

This project uses bd (beads) for issue tracking. Run bd prime for full workflow context.

Quick Reference

bd ready              # Find available work
bd show <id>          # View issue details
bd update <id> --claim  # Claim work atomically
bd close <id>         # Complete work
bd dolt push          # Push beads data to remote

Non-Interactive Shell Commands

ALWAYS use non-interactive flags with file operations to avoid hanging on confirmation prompts.

Shell commands like cp, mv, and rm may be aliased to include -i (interactive) mode on some systems, causing the agent to hang indefinitely waiting for y/n input.

Use these forms instead:

# Force overwrite without prompting
cp -f source dest           # NOT: cp source dest
mv -f source dest           # NOT: mv source dest
rm -f file                  # NOT: rm file

# For recursive operations
rm -rf directory            # NOT: rm -r directory
cp -rf source dest          # NOT: cp -r source dest

Other commands that may prompt:

  • scp - use -o BatchMode=yes for non-interactive
  • ssh - use -o BatchMode=yes to fail instead of prompting
  • apt-get - use -y flag
  • brew - use HOMEBREW_NO_AUTO_UPDATE=1 env var

Beads Issue Tracker

This project uses bd (beads) for issue tracking. Run bd prime to see full workflow context and commands.

Quick Reference

bd ready              # Find available work
bd show <id>          # View issue details
bd update <id> --claim  # Claim work
bd close <id>         # Complete work

Rules

  • Use bd for ALL task tracking — do NOT use TodoWrite, TaskCreate, or markdown TODO lists
  • Run bd prime for the session close protocol. It is not the command index — it omits query, graph, epic, swarm, gate, provenance, compact and flatten. Run bd --help before concluding a capability does not exist.
  • Use bd remember for persistent knowledge — do NOT use MEMORY.md files. A memory is as public as the repo: the database syncs to refs/dolt/data on the git remote, and deleting a memory does not remove it from history. Nothing private goes in one. Full rule: ~/.claude/rules/beads.md ("No user-specific data in shareable artifacts").

Read the full file on GitHub · 111 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. 4d ago Changed · +21 lines · +326 tokens per session f50ba2120342
  2. 1mo ago Changed · +5 lines · +129 tokens per session 40922ad978b3
  3. 1mo ago First seen · 85 lines · 742 tokens per session scan C e1419bb0720d

Subscribe to this mod's changes

braynee AGENTS.md is an instructions file published in the GitHub repository hamchowderr/braynee (2 stars, last pushed 5d ago), licensed MIT. It adds 1,197 tokens to every session, about $0.0048 per session on Opus 5.5. A static security scan graded it C with 2 findings (recursive force delete, makes network calls). It is 75% identical to awesome-spain AGENTS.md, differing in 77 lines, and is treated as a copy.

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