AICaC: Instructions file for Codex

AGENTS.md

AICaC AGENTS.md is an instructions file for Codex, OpenCode from eFAILution/AICaC. It costs 824 tokens per session, scanned A, original, MIT.

Repository instructions for an AI assistant working on AICaC, a convention for storing project context as structured files. They explain which context file to read for different questions.

In plain words
What is it for?
Use them when asking about the project, its architecture, workflows, decisions, errors, or available context keys.
Why use it?
They help the assistant find relevant project information without loading every file, while following the repository’s rules for accuracy and honesty.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md. Also seen: reads .claude/ paths; mentions Claude Code.

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

Reuse

Borrowing it

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

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

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

Your own site · 80×15
<a href="https://agentmods.dev/instructions/efailution/aicac/agents-md"><img src="https://agentmods.dev/badge/instructions/efailution/aicac/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 824 This file is loaded in full into every session.
When invoked 824 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.00824 $0.00824
Opus 5.5 $0.00330 $0.00330
Sonnet 5.5 $0.00165 $0.00165
Haiku 4.5 $0.00082 $0.00082

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

Security

Grade A, and why

AICaC 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 · 63 lines

How it starts

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

AI Assistant Instructions (AICaC repo)

This repository specifies and tools the AI Context as Code (AICaC) v2.0 convention. It dogfoods itself: .ai/ holds structured YAML validated against spec/v2/ JSON Schemas.

Router — load ONLY the relevant file

Each .ai/*.yaml has a top-level summary: field. Read summary first to confirm you've picked the right file before loading the rest. The optional .ai/index.yaml advertises available keys per file without loading content.

Query intent Load this file only
Project overview, entrypoints, dev/test commands .ai/context.yaml
Components, dependencies, data flow .ai/architecture.yaml
How to do X, adoption steps, migration, measurement .ai/workflows.yaml
Why we did X, trade-offs, ADRs .ai/decisions.yaml
Errors, validation failures, troubleshooting .ai/errors.yaml
Which ids/keys exist in each file .ai/index.yaml

Examples:

  • "How do I run the measurements?" → .ai/workflows.yaml → run_token_measurement
  • "Why is v2.0 dict-keyed?" → .ai/decisions.yaml → ADR-008
  • "What does v1.x list form look like?" → .ai/errors.yaml → DEPRECATED_V1_LIST_FORM
  • "What commands can I run?" → .ai/context.yaml → common_tasks

Working on this repo

  • Canonical spec lives in spec/v2/. Every .ai/*.yaml must validate. Run: python3 .github/actions/aicac-adoption/scripts/validate.py .
  • Changes to schemas must include: schema update, whitepaper update, and at least one example file update (this repo's .ai/ and/or validation/examples/sample-project/.ai/).
  • Cross-references (touches_components, affects_components, depends_on, superseded_by) are validator-enforced. Don't add a workflow referencing api if api isn't a component.
  • Token measurements: make measure-all. Results go to experiments/results.json. Checked-in reference: validation/examples/results/.
  • Tests: cd .github/actions/aicac-adoption && pytest
  • Claude Code skill: .claude/skills/aicac/SKILL.md — the on-ramp for Claude Code users to route, bootstrap, validate, and keep .ai/ in sync.

Read the full file on GitHub · 63 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 · 63 lines · 824 tokens per session scan A 731baa6cb6e5

Subscribe to this mod's changes

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

AICaC AGENTS.md compared with instructions from other repositories

AICaC AGENTS.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
AICaC AGENTS.mdeFAILution/AICaCInstructions file53mo agoMITA824Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA9,719GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file143kyesterdayMITA7,461Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchainInstructions file149kyesterdayMITA4,680Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA5,516GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA3,093GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harnessInstructions file274k2d agoMITA4,313Codex, OpenCode