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.
curl -O https://raw.githubusercontent.com/thierry-gilgen-ict/engawa/main/AGENTS.mdgit clone --depth 1 https://github.com/thierry-gilgen-ict/engawaWrote 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.
[](https://agentmods.dev/instructions/thierry-gilgen-ict/engawa/agents-md)<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>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.
| Model | Per session | Once 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 |
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.
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_siteonly 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-nextjspackage in v0.1—document patterns indocs/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 viaENGAWA_MAP_ENDPOINT. RespectENGAWA_CI_REGISTRY_NETWORKin 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).
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.
- 8d ago First seen · 59 lines · 865 tokens per session scan A 2d2d1cdc04d5
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.
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.
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.
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).
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).
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.
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.