AAMS: Instructions file for Codex

AGENTS.md

AAMS AGENTS.md is an instructions file for Codex, OpenCode from ogerly/AAMS. It costs 723 tokens per session, scanned A, original, MIT.

A project-specific instruction file for coding agents working on AAMS. It sets rules for using agents.md, executing work, asking for confirmation, and creating files or directories.

In plain words
What is it for?
Following AAMS-specific instructions before editing files or running tasks.
Why use it?
It gives the agent clear project rules to follow, reducing uncertainty about what actions are allowed.

Instructions file for CodexOpenCode

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

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

Reuse

Borrowing it

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

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

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

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

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

Security

Grade A, and why

AAMS 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 · 74 lines

How it starts

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

AGENTS.md

This file is read automatically by GitHub Copilot, Cursor, Claude Code, OpenAI Codex, Windsurf, Aider, Continue.dev, and most other AI coding agents.

This repository uses AAMS — an agent-contract standard for autonomous work.


Execute now. No confirmation needed.

  1. Read .agent.json — your workspace contract
  2. Read READ-AGENT.md — full project context and session rules
  3. Check state before executing:
    • IF WORKING/WORKPAPER/ does not exist or is empty → Execute agent_contract.on_first_entry
    • IF WORKING/WORKPAPER/ exists and contains workpapers → Execute agent_contract.on_session_start

You MUST

  • Follow the agent contract in READ-AGENT.md
  • Create a workpaper in WORKING/WORKPAPER/ at session start
  • Query WORKING/MEMORY/ for prior context before starting work
  • Complete the workpaper (file protocol + decisions + next steps) at session end
  • Ingest the workpaper into WORKING/MEMORY/ before closing

You MUST NOT

  • Write secrets, tokens, or credentials into any workpaper, whitepaper, or manifest
  • Delete files in WORKING/ — only create and move
  • Skip the file protocol in workpapers

Before Creating Any Directory or File

  • NEVER create utility/tool/script folders in the project root
  • Check WORKING/ structure first — WORKING/TOOLS/ is the designated location for helper scripts, templates, and dev utilities
  • Only create root-level folders if they serve a direct production purpose (e.g., src/, public/, dist/)
  • Before executing any tool: validate its root-anchoring does not point outside WORKING/
  • If a tool uses Path(__file__).resolve().parent.parent or similar offset paths:
    • Verify it still resolves to the correct root for its current location
    • If uncertain: ask before executing

Beispiel: Ein Python-Skript das früher in /tools/ lag und jetzt in /WORKING/TOOLS/ liegt, braucht einen angepassten Root-Pointer. Ein Offset von .parent.parent zeigt fälschlich auf den Agent-Memory statt auf das Projekt.

Read the full file on GitHub · 74 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 · 74 lines · 723 tokens per session scan A 0d37fc4d0137

Subscribe to this mod's changes

AAMS AGENTS.md is an instructions file published in the GitHub repository ogerly/AAMS (7 stars, last pushed 1mo ago), licensed MIT. It adds 723 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-31.

Related

AAMS AGENTS.md compared with instructions from other repositories

AAMS AGENTS.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
AAMS AGENTS.mdogerly/AAMSInstructions file71mo agoMITA723Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA9,719GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file143kyesterdayMITA7,461Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA5,649GitHub Copilot
langchain AGENTS.mdlangchain-ai/langchainInstructions file149ktodayMITA4,680Codex, OpenCode
vscode copilot-instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA3,093GitHub Copilot
vscode ai-customization.instructions.mdmicrosoft/vscodeInstructions file195ktodayMITA1,907GitHub Copilot