Borrowing it
Nothing to install: this file belongs to maxencebernardhub/ai-engineering-labs. 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/maxencebernardhub/ai-engineering-labs/main/AGENTS.mdgit clone --depth 1 https://github.com/maxencebernardhub/ai-engineering-labsWrote 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/maxencebernardhub/ai-engineering-labs/agents-md)<a href="https://agentmods.dev/instructions/maxencebernardhub/ai-engineering-labs/agents-md"><img src="https://agentmods.dev/badge/instructions/maxencebernardhub/ai-engineering-labs/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.00479 | $0.00479 |
| Opus 5 | $0.00239 | $0.00239 |
| Sonnet 5 | $0.00096 | $0.00096 |
| Haiku 4.5 | $0.00048 | $0.00048 |
Grade A, and why
ai-engineering-labs 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 7d 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 — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
Project Overview
Refer to README.md for the full project description, module list, folder structure, and learning paths. Do not duplicate that information here.
Working Rules
- Read the entire target file before modifying it.
- Prefer targeted changes over broad refactors.
- Preserve the pedagogical style and simplicity of examples.
- Do not rename or move existing files without an explicit reason.
- If a single file is sufficient, do not modify several.
- Use the project's local Python environment (
.venv) to run code and tools. - Use
uvto manage the environment, dependencies, and Python commands.
Code Style
- Use simple, explicit Python.
- Prefer descriptive variable names.
- Avoid over-engineering and unnecessary abstractions.
- Document source files clearly with docstrings and useful comments.
- Prefer thorough, pedagogical documentation when it helps understand the code.
- Prefer a runnable, easy-to-read example over a generic architecture.
Python Tools
- Use
uvin preference topiporpython -m pip. - Use project tools from the local environment when possible.
- Maximum line width: 88 characters.
- Follow the Ruff rule families:
E,W,F,I,B,UP.
Lab Conventions
- Create numbered files with a two-digit prefix when relevant.
- Maintain a pedagogical progression from simplest to most advanced.
- Each lab must illustrate one clearly identifiable main idea.
- Avoid mixing too many concepts in the same file.
- Keep dependencies to a strict minimum.
Validation
- Verify the syntax of any modified file when possible.
- Do not add a dependency without an explicit request.
- Report when a verification could not be run.
Security & Safety
- Never read, modify, or commit
.envfiles or any file containing secrets or credentials — treat them as off-limits entirely. - Never access environment variables or secret values that are not strictly required by the current task.
- Ask before changing the global project structure.
- Flag any ambiguity about expected behavior before acting.
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.
- 7d ago First seen · 65 lines · 479 tokens per session scan A 378aa17493a8
ai-engineering-labs AGENTS.md is an instructions file published in the GitHub repository maxencebernardhub/ai-engineering-labs (2 stars, last pushed 1mo ago), licensed MIT. It adds 479 tokens to every session, about $0.0024 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
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).
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.
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.
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).
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.