engawa: Instructions file for Codex

AGENTS.md

engawa AGENTS.md is an instructions file for Codex, OpenCode from thierry-gilgen-ict/engawa. It costs 865 tokens per session, scanned A, original, MIT.

Repository guidance for coding agents working with Engawa, an open toolkit that publishes website content in formats that both people and software agents can read.

In plain words
What is it for?
Use it when developing Engawa, checking its published packages, or adding Engawa’s agent-readable content and read-only MCP access to another website.
Why use it?
It gives agents the project’s purpose, package details, required Node.js version, defaults, and rules in one place.

Instructions file for CodexOpenCode

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

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

Reuse

Borrowing it

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

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

README.md
[![agentmods](https://agentmods.dev/badge/instructions/thierry-gilgen-ict/engawa/agents-md.svg)](https://agentmods.dev/instructions/thierry-gilgen-ict/engawa/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/thierry-gilgen-ict/engawa/agents-md"><img src="https://agentmods.dev/badge/instructions/thierry-gilgen-ict/engawa/agents-md.svg" alt="Measured on agentmods" height="20"></a>
Per session 865 This file is loaded in full into every session.
When invoked 865 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.00865 $0.00865
Opus 5 $0.00432 $0.00432
Sonnet 5 $0.00173 $0.00173
Haiku 4.5 $0.00086 $0.00086

Measured 8d ago against content hash 2d2d1cdc04d5, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

engawa 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 8d 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 · 59 lines

How it starts

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

AGENTS.md

Orientation for coding agents working in or with the Engawa repository.

What Engawa is

Open toolkit for agent-native websites: human HTML plus structured agent surfaces (llms.txt, markdown alternates, read-only MCP, optional Bring Your Agent UI). Agents can read HTML; Engawa exposes the same human-public content through cleaner bounded representations—see do-you-need-engawa.md and ADR-0008.

Current published packages (npm)

Package Version
@thierry-gilgen-ict/engawa-core 0.1.1
@thierry-gilgen-ict/engawa-discovery 0.2.0
@thierry-gilgen-ict/engawa-mcp 0.1.1
@thierry-gilgen-ict/engawa-react 0.1.0
@thierry-gilgen-ict/engawa-map 0.1.0
@thierry-gilgen-ict/engawa-cli 0.1.0

Node.js 24+ required (engines in package manifests).

Package versions may diverge by design. See docs/compatibility.md.

Defaults and invariants

  • Public Engawa is read-only by default (v0.1: search_site only on public MCP).
  • Generic MCP is the canonical fallback for provider UX—not fake one-click connects.
  • Content parity: HUMAN_PUBLIC_SOURCE == ENGAWA_SOURCE (content publication rule).
  • No engawa-nextjs package in v0.1—document patterns in docs/integrations/ (including headless CMS).
  • Do not expose secrets, sessions, drafts, or admin-only corpus on public surfaces.
  • Do not register a site on the Distribution Map without explicit user request (DO_NOT_REGISTER_MAP_WITHOUT_EXPLICIT_USER_REQUEST).
  • Distribution Map CLI is published (@thierry-gilgen-ict/[email protected]); production registry is live. Staging remains available via ENGAWA_MAP_ENDPOINT. Respect ENGAWA_CI_REGISTRY_NETWORK in tests. See distribution-map-api.md.
  • Do not execute application config or import app modules for map registration (DO_NOT_EXECUTE_APPLICATION_CONFIG_FOR_MAP; ENGAWA_MAP_EXECUTES_APPLICATION_CODE = NO).
  • Do not place map tokens in website runtime, MCP, or React (DO_NOT_USE_MAP_TOKEN_IN_WEBSITE_RUNTIME).

Read the full file on GitHub · 59 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. 8d ago First seen · 59 lines · 865 tokens per session scan A 2d2d1cdc04d5

Subscribe to this mod's changes

engawa AGENTS.md is an instructions file published in the GitHub repository thierry-gilgen-ict/engawa (5 stars, last pushed 3d ago), licensed MIT. It adds 865 tokens to every session, about $0.0043 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

next.js AGENTS.md

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

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,153 tokens

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

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

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,469 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