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/wackygem/fleur/agents-mdgit clone --depth 1 https://github.com/WackyGem/FleurWhat 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.03914 | $0.03914 |
| Opus 5 | $0.01957 | $0.01957 |
| Sonnet 5 | $0.00783 | $0.00783 |
| Haiku 4.5 | $0.00391 | $0.00391 |
Grade A, and why
Fleur 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 2d 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 — 264 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — fleur 项目指南
项目结构
fleur/
├── pipeline/ # Python 数据工作区，由 uv 管理
│ ├── scheduler/ # Dagster 调度项目（scheduler）
│ ├── elt/ # dbt 转换项目（elt）
│ ├── contract_tools/ # 数据契约校验与生成工具
│ ├── contracts/ # 数据契约注册表（字段事实源）
│ └── migrate/ # Alembic 数据库迁移
├── engines/ # Rust 后端和计算引擎工作区，由 Cargo 管理
├── deploy/ # 部署配置
│ ├── docker-compose.yml
│ ├── postgres/ # PostgreSQL 配置
│ └── release-manifest.yml
├── app/ # 前端应用工作区（racingline）
├── docs/ # 项目文档与计划
├── .env # 环境变量（不提交）
└── .env.example # 环境变量模板
文档入口
- 文档总入口：
docs/README.md - 多工程项目状态：
docs/architecture/project-status.md - 数据平台地图：
docs/architecture/data-platform.md - 数据治理地图：
docs/architecture/data-governance.md - Furnace 计算引擎地图：
docs/architecture/furnace.md - Rearview 后端服务地图：
docs/architecture/rearview.md - Racingline 前端工作台地图：
docs/architecture/racingline.md - 部署与运行地图：
docs/architecture/deploy-ops.md - 架构边界：
docs/architecture/ - 模块边界：
docs/architecture/scheduler-module-boundaries.md - 长期决策：
docs/ADR/ - 方案与历史设计：
docs/RFC/ - 执行计划：
docs/plans/README.md - 技术债与质量优化：
docs/issues/ - 运行报告：
docs/jobs/reports/ - dbt 模型设计：
docs/architecture/dbt_layer/ - 接口、数据字典和样例：
docs/references/ - 项目 skills：
docs/skills/ - Rust engines 文档地图：
engines/README.md
Python 与工作区
- 使用
uv管理 Python 依赖和虚拟环境。 - Python 版本固定在
3.12.13，配置于pipeline/.python-version。 - 所有 Python、dbt、Dagster 和
dg命令必须在pipeline/目录下通过uv run执行。 - 同步完整工作区：
cd pipeline
uv sync --all-packages --all-groups
子项目
| 子项目 | 路径 | 包管理器 | 说明 |
|---|---|---|---|
| scheduler | pipeline/scheduler/ |
uv (pyproject.toml) | Dagster 调度与资产定义 |
| elt | pipeline/elt/ |
uv (pyproject.toml) | dbt 数据转换 |
| contract_tools | pipeline/contract_tools/ |
uv (pyproject.toml) | contract registry 校验与生成 |
| migrate | pipeline/migrate/ |
uv (pyproject.toml) | Alembic 数据库迁移 |
Rust 与 engines 工作区
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.
- 2d ago First seen · 264 lines · 3,914 tokens per session scan A 1ff6771fcff0
Fleur AGENTS.md is an instructions file published in the GitHub repository WackyGem/Fleur (110 stars, last pushed 1mo ago), licensed MIT. It adds 3,914 tokens to every session, about $0.0196 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-30.
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
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
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.
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.