facility: Instructions file for Codex

AGENTS.md

facility AGENTS.md is an instructions file for Codex, OpenCode from theam/facility. It costs 717 tokens per session, scanned A, original, Apache-2.0.

Repository instructions for facility AGENTS.md, covering engineering rules, tests for security- and money-sensitive changes, and commit subjects that control released versions.

In plain words
What is it for?
Use them when changing authentication, permissions, tenant access, secrets, cryptography, billing, budgets, webhooks, or privileged integrations, and when writing commits.
Why use it?
They make risky changes harder to ship without the required tests and keep commit history compatible with automatic version releases.

Instructions file for CodexOpenCode

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

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

Reuse

Borrowing it

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

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

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/theam/facility/agents-md"><img src="https://agentmods.dev/badge/instructions/theam/facility/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 717 This file is loaded in full into every session.
When invoked 717 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.00717 $0.00717
Opus 5.5 $0.00287 $0.00287
Sonnet 5.5 $0.00143 $0.00143
Haiku 4.5 $0.00072 $0.00072

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

Security

Grade A, and why

facility 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 · 56 lines

How it starts

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

Engineering instructions

Critical-change regression coverage

Changes to security- or money-critical surfaces—including authentication, authorization/RBAC, tenant scoping, secrets and cryptography, billing or budget enforcement, webhook signature validation, and privileged external integrations—are incomplete without both unit tests and integration tests.

Integration tests must use deterministic fakes or local servers for external systems. The default CI suite must not need live credentials or network access. Cover successful operation and relevant denial paths, including malformed, expired, revoked, replayed, and cross-tenant inputs. Add a regression test that would fail if the previous unsafe behavior returned.

Commit subjects set the released version

Write every commit subject as a Conventional Commit:

<type>[(scope)][!]: <what changed>

Use one of these types: feat, fix, perf, docs, style, refactor, test, build, ci, chore, or revert.

This is not a style preference. Release-on-merge derives the next version from the subjects merged since the last release. Subject validation lands before that workflow so the history it will consume is already trustworthy: a subject that lies about the kind of change ships the wrong version number to everyone who installed the package.

Subject What it releases while the version is 0.x
fix: …, perf: …, revert: … a patch
feat: … a patch
<type>!: …, or a BREAKING CHANGE: footer a minor
docs: …, test: …, refactor: …, ci: …, chore: …, build: …, style: … nothing on its own

Two consequences worth internalising:

  • A user-visible change hidden behind chore: never reaches users. It sits on main unreleased until something else triggers a release, and then ships unannounced in someone else's release notes.
  • A breaking change without ! ships as a patch. Mark it, in the subject or in a BREAKING CHANGE: footer, and say in the body what a user has to change.

Read the full file on GitHub · 56 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. 2mo ago First seen · 56 lines · 717 tokens per session scan A f479c90dee07

Subscribe to this mod's changes

facility AGENTS.md is an instructions file published in the GitHub repository theam/facility (88 stars, last pushed yesterday), licensed Apache-2.0. It adds 717 tokens to every session, about $0.0029 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

facility AGENTS.md compared with instructions from other repositories

facility AGENTS.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
facility AGENTS.mdtheam/facilityInstructions file88yesterdayApache-2.0A717Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA9,719GitHub Copilot
vscode oss-third-party-notices.instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA5,516GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file143kyesterdayMITA7,461Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchainInstructions file149ktodayMITA4,680Codex, OpenCode
vscode copilot-instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA3,093GitHub Copilot
vscode model-prompts.instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA2,022GitHub Copilot