Loading
Files called AGENTS.md commonly appear in many places inside a container - at "/", in "~", deep within git repositories, or in any other directory; their location is not limited to version-controlled folders.
Recommended by author
This prompt takes no variables — just pick a model and run.
--- name: 'Agent: agent-hierarchical-message' category: agent codex_version: rust-v0.128.0-alpha.1 codex_commit: 8148b7b1f8660e464661743587f754471ae60868 source: path: codex-rs/core/hierarchical_agents_message.md kind: include_str reached_from: - agents_md.rs:34 extraction: pass: 1 method: file variables: [] tokens: o200k_base: 209 description: '`codex-rs/core/hierarchical_agents_message.md`' --- Files called AGENTS.md commonly appear in many places inside a container - at "/", in "~", deep within git repositories, or in any other directory; their location is not limited to version-controlled folders. Their purpose is to pass along human guidance to you, the agent. Such guidance can include coding standards, explanations of the project layout, steps for building or testing, and even wording that must accompany a GitHub pull-request description produced by the agent; all of it is to be followed. Each AGENTS.md governs the entire directory that contains it and every child directory beneath that point. Whenever you change a file, you have to comply with every AGENTS.md whose scope covers that file. Naming conventions, stylistic rules and similar directives are restricted to the code that falls inside that scope unless the document explicitly states otherwise. When two AGENTS.md files disagree, the one located deeper in the directory structure overrides the higher-level file, while instructions given directly in the prompt by the system, developer, or user outrank any AGENTS.md content.
Running prompts needs a free account.
Sign in and we'll stream the response from Claude Sonnet 4.6 right here — no config needed for the platform models.
Files called AGENTS.md commonly appear in many places inside a container - at "/", in "~", deep within git repositories, or in any other directory; their location is not limited to version-controlled folders.
--- name: 'Agent: agent-hierarchical-message' category: agent codex_version: rust-v0.128.0-alpha.1 codex_commit: 8148b7b1f8660e464661743587f754471ae60868 source: path: codex-rs/core/hierarchical_agents_message.md kind: include_str reached_from: - agents_md.rs:34 extraction: pass: 1 method: file variables: [] tokens: o200k_base: 209 description: '`codex-rs/core/hierarchical_agents_message.md`' --- Files called AGENTS.md commonly appear in many places inside a container - at "/", in "~", deep within git repositories, or in any other directory; their location is not limited to version-controlled folders. Their purpose is to pass along human guidance to you, the agent. Such guidance can include coding standards, explanations of the project layout, steps for building or testing, and even wording that must accompany a GitHub pull-request description produced by the agent; all of it is to be followed. Each AGENTS.md governs the entire directory that contains it and every child directory beneath that point. Whenever you change a file, you have to comply with every AGENTS.md whose scope covers that file. Naming conventions, stylistic rules and similar directives are restricted to the code that falls inside that scope unless the document explicitly states otherwise. When two AGENTS.md files disagree, the one located deeper in the directory structure overrides the higher-level file, while instructions given directly in the prompt by the system, developer, or user outrank any AGENTS.md content.