What is engineering-board AGENTS.md?

Repository instructions for developers and coding agents working on the Engineering Board project. They describe the files and process required for release changes.

Use them when changing Engineering Board releases, versions, checksums, tags, or publication materials.

They reduce the risk of incomplete or inconsistent releases by requiring coordinated version, checksum, tag, and publication updates.

How GhostlyGawd/engineering-board configures Codex and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to GhostlyGawd/engineering-board. 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/GhostlyGawd/engineering-board/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/GhostlyGawd/engineering-board

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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/ghostlygawd/engineering-board/agents-md/github.svg)](https://agentmods.dev/instructions/ghostlygawd/engineering-board/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/ghostlygawd/engineering-board/agents-md"><img src="https://agentmods.dev/badge/instructions/ghostlygawd/engineering-board/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/ghostlygawd/engineering-board/agents-md"><img src="https://agentmods.dev/badge/instructions/ghostlygawd/engineering-board/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

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

Model	Per session	Once invoked
Fable 5.1	$0.00503	$0.00503
Opus 5.5	$0.00201	$0.00201
Sonnet 5.5	$0.00101	$0.00101
Haiku 4.5	$0.00050	$0.00050

Measured 2mo ago against content hash 156b36e98b49, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

engineering-board 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 2mo 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 · 51 lines

How it starts

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

Repository agent instructions

Development team

Follow docs/DEVELOPMENT.md for maintainer product work. Use a lead, a builder, and an independent verifier with one accountable owner per board entry. Delegate bounded review and implementation assignments when they can progress independently. Record scope and acceptance criteria before implementation; review substantive changes in a fresh agent context. Existing user authorization covers routine implementation and delivery. Changes to product goals or evaluation success criteria require a concrete owner decision. The lead records evidence and resolves entries only after the required review.

Release work

For Engineering Board release work, read these files before you change a version, checksum, tag, release, or publication:

maintainers/skills/release-engineering-board/SKILL.md
docs/RELEASING.md

Use scripts/prepare-release.py for the coordinated release change. Do not change one versioned surface independently.

Do not use the maintainer release skill in a repository that only installs the Engineering Board plugin.

The owner approved the current controlled-English text. Do not claim formal ASD-STE100 compliance without a separate qualified verification.

engineering-board

This repo tracks its work on a markdown board under engineering-board/ (bugs, features, questions, observations, learnings, and hypotheses). BOARD.md is a derived index; never edit it by hand, the tools rebuild it. If you can call the engineering-board MCP tools, use the board:

Capture findings as you notice them: board_capture_finding (project, kind, title).
List actionable work: board_list_entries with ready: true.
Claim an entry BEFORE working on it: board_claim (project, entry_id, session_id).
Record progress on the entry: board_update_entry (status, needs, comment).
Promote a finding to a real entry: board_create_entry.
Save a durable insight: board_remember (project, insight).
Rank systemic investigations: board_insights (project).
Preserve or evaluate a cited root-cause claim: preview/apply with board_hypotheses.
When done: board_update_entry to the new status, then board_release.

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

2mo ago Changed · +32 lines · +371 tokens per session 156b36e98b49
2mo ago First seen · 19 lines · 132 tokens per session scan A 65cfb95da87f

Subscribe to this mod's changes

engineering-board AGENTS.md is an instructions file published in the GitHub repository GhostlyGawd/engineering-board (0 stars, last pushed 2d ago), licensed MIT. It adds 503 tokens to every session, about $0.0020 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-31.

engineering-board AGENTS.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
engineering-board AGENTS.mdGhostlyGawd/engineering-board	Instructions file	0	2d ago	MIT	A	503	Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	today	MIT	A	7,461	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	5,685	GitHub Copilot
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	3,093	GitHub Copilot
vscode model-prompts.instructions.mdmicrosoft/vscode	Instructions file	195k	today	MIT	A	2,022	GitHub Copilot

engineering-board: Instructions file for Codex