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.
npx agentmods add instructions/amadeus-dlc/amadeus/agents-mdgit clone --depth 1 https://github.com/amadeus-dlc/amadeusWrote 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/amadeus-dlc/amadeus/agents-md)<a href="https://agentmods.dev/instructions/amadeus-dlc/amadeus/agents-md"><img src="https://agentmods.dev/badge/instructions/amadeus-dlc/amadeus/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 | $0.01698 | $0.01698 |
| Opus 5 | $0.00849 | $0.00849 |
| Sonnet 5 | $0.00340 | $0.00340 |
| Haiku 4.5 | $0.00170 | $0.00170 |
Grade A, and why
amadeus 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 4d 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 — 95 lines — stays where its author put it; the contents beside it link to each section on GitHub.
@.agents/rules/amadeus.md @.agents/rules/amadeus-codex-suffix.md
To avoid collisions with other agents, always create a dedicated worktree and branch and switch to them before starting work.
AGENTS.md
Behavioral guidelines to reduce common LLM coding mistakes. Merge with project-specific instructions as needed.
Tradeoff: These guidelines bias toward caution over speed. For trivial tasks, use judgment.
Project Instructions
- Communicate with the user in Japanese.
- Write documentation in English by default.
- As an exception, write
amadeus/**/*.mdin Japanese. - Write code comments in English.
- Write commit messages in English.
- If you find violations of these language rules while working, fix them as part of the same change.
- For Amadeus self-development, explicitly select
self-feature,self-fix,self-refactor, orself-documentbased on the change type. The canonical policy isamadeus/spaces/default/memory/project.md§ Scope Overrides.
1. Think Before Coding
Don't assume. Don't hide confusion. Surface tradeoffs.
Before implementing:
- State your assumptions explicitly. If uncertain, ask.
- If multiple interpretations exist, present them - don't pick silently.
- If a simpler approach exists, say so. Push back when warranted.
- If something is unclear, stop. Name what's confusing. Ask.
2. Simplicity First
Minimum code that solves the problem. Nothing speculative.
- No features beyond what was asked.
- No abstractions for single-use code.
- No "flexibility" or "configurability" that wasn't requested.
- No error handling for impossible scenarios.
- If you write 200 lines and it could be 50, rewrite it.
Ask yourself: "Would a senior engineer say this is overcomplicated?" If yes, simplify.
3. Surgical Changes
Touch only what you must. Clean up only your own mess.
When editing existing code:
- Don't "improve" adjacent code, comments, or formatting.
- Don't refactor things that aren't broken.
- Match existing style, even if you'd do it differently.
- If you notice unrelated dead code, mention it - don't delete it.
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.
- 4d ago First seen · 95 lines · 1,698 tokens per session scan A 26cba62ba3c3
amadeus AGENTS.md is an instructions file published in the GitHub repository amadeus-dlc/amadeus (8 stars, last pushed 13d ago), licensed Apache-2.0. It adds 1,698 tokens to every session, about $0.0085 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
FrameCode-VibeWork AGENTS.md
AGENTS.md instructions for Sistema2D/FrameCode-VibeWork, covering agents.md, instruction order, reading-trigger rule, regression rule and when a plan is required.
plainweave AGENTS.md
AGENTS.md instructions for foundryside-dev/plainweave, covering filigree issue tracker, workflow, at session start, ...or claim a specific issue and do the work, commit, then.
plainweave CLAUDE.md
Claude Code instructions for foundryside-dev/plainweave, covering filigree issue tracker, workflow, at session start, ...or claim a specific issue and do the work, commit, then.
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).
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.
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.