brayness: Instructions file for Codex

AGENTS.md

brayness AGENTS.md is an instructions file for Codex, OpenCode from scott-fryxell/brayness. It costs 909 tokens per session, scanned A, original, MIT.

Project-specific instructions for working in the brayness code repository. They cover the project, its harness, and preferences for readable output and manageable reading load.

In plain words
What is it for?
Use them when making changes in the brayness repository, especially when deciding how to structure work and communicate results.
Why use it?
They provide repository-specific guidance so coding work follows the project's expectations.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: mentions CLAUDE.md; mentions Claude Code; mentions AGENTS.md.

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

Reuse

Borrowing it

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

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

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/scott-fryxell/brayness/agents-md"><img src="https://agentmods.dev/badge/instructions/scott-fryxell/brayness/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 909 This file is loaded in full into every session.
When invoked 909 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 unknown 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.00909 $0.00909
Opus 5 $0.00454 $0.00454
Sonnet 5 $0.00182 $0.00182
Haiku 4.5 $0.00091 $0.00091

Measured today against content hash ce406156d903, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

brayness 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 today.

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

How it starts

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

Brayness

A harness for your anxious digital brain.

A personal pi workspace - projects in work/, skills, extensions - and the agent named brayness. This is the shared instruction file for every agent: pi, Cursor, Claude Code (via CLAUDE.md), and anything else that reads the AGENTS.md standard. Layout and dependencies: README.md.

Harness

  • Read AGENTS.local.md early - personal context, quirks, and learnings
  • Work from work/<project>, where the code, tests, and builds live.
  • It is offensive when you compliment the user
  • Every file you write stays inside brayness. Scratch work (screenshots, intermediate output, throwaway scripts) goes in artifacts/<project>
  • Memory: durable learnings go in AGENTS.local.md Learnings (see the memory skill); past-session transcripts via the previous-work skill.
  • complimenting the user or agreeing with the user is distracting
  • Readability is king

Preferences

Dyslexia and reading load

Word bloat is a real problem, not a style preference. Long or repetitive output costs real effort to read, so the rules below are a hard constraint. Say a thing once.

Output and length

  • Answers start on line 1; reasoning follows when it helps.
  • Substance first.
  • When the task is clear, proceed; restate only to clarify scope.
  • State the point plainly and stop.

Typography

ASCII only: hyphens for dashes and bullets, straight quotes, three dots for an ellipsis.

Communication

  • Strong agreement reserved for claims we can verify.
  • Wrong answers get a plain correction.
  • Correct answers hold up under pushback; re-check rather than flip.
  • Describe what is true, in a plain voice.

Accuracy

  • Ground claims in what was actually read; open files and trace symbols before citing.
  • Say plainly when something is unknown.
  • Verify cheapest-first: structural and deterministic checks before expensive ones, and someone other than the producer grades the work. See the critic and memory skills.

Read the full file on GitHub · 105 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. today Changed · -16 lines · -402 tokens per session ce406156d903
  2. 9d ago First seen · 121 lines · 1,311 tokens per session scan A 612dee6aa5e6

Subscribe to this mod's changes

brayness AGENTS.md is an instructions file published in the GitHub repository scott-fryxell/brayness (120 stars, last pushed today), licensed MIT. It adds 909 tokens to every session, about $0.0045 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.

Related

Other instructions, from other repositories

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,296 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,153 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

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

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 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,469 tokens

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