agentmods.dev

eou-foundry AGENTS.md

Repository instructions for eou-foundry, including prerequisites, validation commands, project rules, and the approved vocabulary for its schemas and automation files.

In plain words
What is it for?
Use them when changing schemas, validation code, skills, rules, metadata, or the local setup required to run the project’s checks.
Why use it?
They help keep schema values and related documentation consistent across validators, skills, rules, and metadata.

Instructions file for CodexOpenCode

10 9d ago A scan 1,737 tokens original ISC
View the source file xiaolai/eou-foundry
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add instructions/xiaolai/eou-foundry/agents-md
Clone the repo
git clone --depth 1 https://github.com/xiaolai/eou-foundry

Made for: Codex, OpenCode.

Per session 1,737 This file is loaded in full into every session.
When invoked 1,737 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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 $0.01737 $0.01737
Opus 5 $0.00869 $0.00869
Sonnet 5 $0.00347 $0.00347
Haiku 4.5 $0.00174 $0.00174

Measured 3d ago against content hash a6cf9edd34be, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

eou-foundry 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 3d 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 · 114 lines

How it starts

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

Project Instructions

eou-foundry

Prerequisites

  • Python 3.9+ — required by scripts/validate_foundry.py and the helper modules under scripts/.
  • PyYAML (pip install pyyaml) — the validator reads/writes YAML.
  • No other runtime dependencies for validation. CI may additionally need gh for ECP submission flows; local development does not.
  • EOU_FOUNDRY_PLUGIN_PATH environment variable should point at the plugin checkout when running validate_foundry.py outside an installed-plugin context (the validator falls back to installed_plugins.json and then to its own parent directory).

Guidelines

Vocabulary authority chain

schemas/ is the ground truth for all enum values. When vocabulary changes:

  1. Update the schema file (schemas/eou.schema.yml or schemas/ecp.schema.yml)
  2. Update scripts/validate_foundry.py (VALID_FUNCTIONS, VALID_AUTOMATION, VALID_AUTHORITY, VALID_RISK, VALID_STAGE)
  3. Update every skill in skills/ that references the changed enum
  4. Update every matching codex skill in codex/skills/
  5. Update every rule in rules/ that documents the enum
  6. Update any meta-EOU in engine/meta-eous/ that uses the value

Never update vocabulary in only one place — all six layers must stay in sync.

Testing changes

After editing any script, run the validator against the fixture foundry:

python3 scripts/validate_foundry.py tests/fixture-foundry

After editing any SKILL.md, verify the output path it declares matches the path the consuming skill (eou-promote, eou-diagnose, eou-refactor, foundry-audit, audit-candidate-eou-set) reads from.

Skill selection guide

Goal Use
Synthesize Stage 0 inputs from references (literacy bridge + per-app constitutional layer) $generate-captured-workflow-from-references
Convert workflow → candidate EOUs $generate-eou-candidates (consults captured_workflow when present per Rule 96)
Audit a candidate set for readiness $audit-candidate-eou-set (runs Set Value Coverage Test when captured_workflow present)
Convert approved candidate → spec $eou-specify
Audit a spec for V2 compliance $eou-audit (runs Value Operationalization Test when captured_workflow present per Rule 96)
Audit agentic-judgment invocations (F14–F17 + counterfactual-swap) $audit-judgment (fourth audit layer per D4.1; enforces Rule 97 on EOUs with judgment_authorized:true)
Audit the whole foundry $foundry-audit
Validate schemas and registry $eou-validate
Diagnose a failure $eou-diagnose
Generate refactor options $eou-refactor
Propose a structural change $ecp-propose
Promote or retire a spec $eou-promote
Convert incidents → regression cases $generate-regression-cases
Scaffold a new app $eou-foundry-init (Codex-only)

Read the full file on GitHub · 114 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. 3d ago First seen · 114 lines · 1,737 tokens per session scan A a6cf9edd34be

Subscribe to this mod's changes

eou-foundry AGENTS.md is an instructions file published in the GitHub repository xiaolai/eou-foundry (10 stars, last pushed 9d ago), licensed ISC. It adds 1,737 tokens to every session, about $0.0087 per session on Opus 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

Other instructions, from other repositories

vscode buildNext.instructions.md

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 6,785 tokens

spec-kit AGENTS.md

AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,104 tokens

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,182 tokens

langchain AGENTS.md

AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,345 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

next.js AGENTS.md

Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens