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/b-fontaine/devoxx-2026/agents-mdgit clone --depth 1 https://github.com/b-fontaine/devoxx-2026Wrote 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/b-fontaine/devoxx-2026/agents-md)<a href="https://agentmods.dev/instructions/b-fontaine/devoxx-2026/agents-md"><img src="https://agentmods.dev/badge/instructions/b-fontaine/devoxx-2026/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.02142 | $0.02142 |
| Opus 5 | $0.01071 | $0.01071 |
| Sonnet 5 | $0.00428 | $0.00428 |
| Haiku 4.5 | $0.00214 | $0.00214 |
Grade A, and why
devoxx-2026 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 5d 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 — 211 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — Instructions cross-agents
Projet
Frontend Flutter (Clean Architecture) + Backend Rust (Architecture Hexagonale).
Architecture
Frontend — Clean Architecture (Flutter)
frontend/lib/
├── core/ # Shared: errors, network, DI setup
└── features/
└── <feature_name>/
├── domain/ # Entities, Repository contracts (abstract), Use Cases
├── data/ # Models, DataSources, Repository implementations
└── presentation/ # Bloc/Cubit, Pages, Widgets
Backend — Architecture Hexagonale (Rust)
backend/src/
├── domain/ # Traits (ports), entités, erreurs métier
├── application/ # Use cases, orchestration
└── infrastructure/ # Adaptateurs : HTTP/REST (axum), persistence (sea-orm)
Règles d'architecture — VIOLATIONS INTERDITES
- INTERDIT : importer
infrastructure/oudata/depuisdomain/. Le domain ne dépend de RIEN. - INTERDIT : importer
data/depuispresentation/. La dépendance estpresentation → domain ← data. - INTERDIT : mettre de la logique métier dans un Widget, une Page, ou un handler HTTP/REST. La logique métier vit dans
domain/etapplication/uniquement. - INTERDIT : écrire un test qui dépend d'un service externe réel. Toujours mocker les ports/traits.
- INTERDIT : utiliser
unwrap()en code de production Rust. Réservé aux tests uniquement.
Conventions de code
Dart/Flutter
- State management :
flutter_blocuniquement (pas de Provider direct, pas de setState pour la logique) - DI :
get_it+injectable - Erreurs :
Either<Failure, T>viadartz - Tests BDD :
bdd_widget_testavec.featureGherkin - Génération de code :
build_runner(freezed, injectable, retrofit)
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.
- 5d ago First seen · 211 lines · 2,142 tokens per session scan A 5b0994cc7261
devoxx-2026 AGENTS.md is an instructions file published in the GitHub repository b-fontaine/devoxx-2026 (5 stars, last pushed 4mo ago), licensed MIT. It adds 2,142 tokens to every session, about $0.0107 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
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.
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.
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.