OpenAva: Instructions file for Codex

AGENTS.md

OpenAva AGENTS.md is an instructions file for Codex, OpenCode from Day1Labs/OpenAva. It costs 550 tokens per session, scanned A, original, MIT.

Repository instructions for OpenAva that define how a coding agent should understand requirements, inspect code, make changes, simplify them, and verify the result.

In plain words
What is it for?
Use them to guide work involving new requirements, entities, existing code flows, implementation scope, cleanup, and verification.
Why use it?
They reduce unnecessary changes and require direct checks such as tests, compilation, or path validation before reporting success.

Instructions file for CodexOpenCode

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

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

Reuse

Borrowing it

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

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

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/day1labs/openava/agents-md"><img src="https://agentmods.dev/badge/instructions/day1labs/openava/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 550 This file is loaded in full into every session.
When invoked 550 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.00550 $0.00550
Opus 5.5 $0.00220 $0.00220
Sonnet 5.5 $0.00110 $0.00110
Haiku 4.5 $0.00055 $0.00055

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

Security

Grade A, and why

OpenAva 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 · 35 lines

How it starts

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

Agent Operating Rules

Goal: complete the user's current requirement with the lowest necessary complexity, and make the result easy to verify and explain.

Highest Priority (Hard Rules)

  • State the requirement before acting: summarize the user-visible behavior change in 1 sentence. If uncertain, ask only the minimum necessary clarification.
  • Read before changing: inspect the relevant files/types before editing, and make the smallest change that fits the existing structure.
  • Prefer existing flows: if the requirement can be solved inside existing types/functions/flows, do not add a manager / wrapper / service / helper.
  • Do not design for the future: do not solve hypothetical future needs; do not add extension points unless the current task clearly requires them.
  • Simplify after it works: after the first working version, do one simplification pass to remove dead code, redundant branches, one-off parameters, and misleading names.
  • Verification is required: validate the change using the most direct available method (tests / compile / direct path validation). “It should work” is not enough.

Triggered Rules (When / Then)

  • When adding a new entity: first prove that modifying the existing code cannot express the requirement cleanly. Then explain why the new entity is necessary, what it owns, and why editing the existing code was not enough.
  • When two solutions both work: choose the one with fewer new concepts, fewer lines of code, and fewer indirection layers.
  • When a change touches multiple modules: keep data flow explicit, with clear ownership of parameters, return values, and state. Avoid hidden global state or opaque cross-layer flow.
  • When fixing a bug: state the reproduction condition or visible failure first, then make the smallest fix, then add a regression validation point.

Anti-Patterns

  • Adding a new abstraction only to avoid editing the existing code
  • Adding a helper/wrapper used only once, unless it clearly improves readability and removes duplication
  • Keeping dead branches or compatibility code “just in case”
  • Skipping verification after changes

Read the full file on GitHub · 35 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 · 35 lines · 550 tokens per session scan A 7f4bf40500ad

Subscribe to this mod's changes

OpenAva AGENTS.md is an instructions file published in the GitHub repository Day1Labs/OpenAva (11 stars, last pushed 3mo ago), licensed MIT. It adds 550 tokens to every session, about $0.0022 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.

Related

OpenAva AGENTS.md compared with instructions from other repositories

OpenAva AGENTS.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
OpenAva AGENTS.mdDay1Labs/OpenAvaInstructions file113mo agoMITA550Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA9,719GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file143ktodayMITA7,461Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA5,516GitHub Copilot
langchain AGENTS.mdlangchain-ai/langchainInstructions file149kyesterdayMITA4,680Codex, OpenCode
vscode copilot-instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA3,093GitHub Copilot
vscode ai-customization.instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA1,907GitHub Copilot