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 skills/wackygem/fleur/fleur-contract-data-dictionarynpx skills add WackyGem/Fleur --skill fleur-contract-data-dictionarygit clone --depth 1 https://github.com/WackyGem/FleurWrote 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/skills/wackygem/fleur/fleur-contract-data-dictionary)<a href="https://agentmods.dev/skills/wackygem/fleur/fleur-contract-data-dictionary"><img src="https://agentmods.dev/badge/skills/wackygem/fleur/fleur-contract-data-dictionary.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.00089 | $0.02013 |
| Opus 5 | $0.00044 | $0.01007 |
| Sonnet 5 | $0.00018 | $0.00403 |
| Haiku 4.5 | $0.00009 | $0.00201 |
Grade A, and why
fleur-contract-data-dictionary 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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fleur Contract Data Dictionary
当任务涉及 pipeline/contracts、pipeline/contract_tools、scheduler Parquet schema 边界、docs/references/data_dict、dbt sources.yml 的 raw 字段事实、中文字段描述或生成物同步时，使用这个 skill。
核心边界
- 字段事实源是
pipeline/contracts/datasets/*.yml，范围到 ClickHouse raw 层为止。 pipeline/contracts/glossary/tables.yml只维护 raw table 描述，不维护字段或 canonical 字段名。parquet.fields是source -> S3 Parquet -> ClickHouse raw的 Parquet 字段、类型、nullable 和顺序事实源。docs/references/data_dict/*.md、pipeline/elt/models/sources.yml是生成物，不作为字段事实源。- dbt canonical 字段治理入口是
pipeline/elt/metadata/field_glossary.yml。 - dbt
staging.yml、stg_*.sql、stg 字段描述、tests 和 meta 由pipeline/elt项目维护，不写入数据契约。 - 修改字段事实时先改 dataset contract，再运行生成器；不要手工修 generated data_dict 或 dbt
sources.yml。 - 所有 Python、dbt、contract 命令在
pipeline/下通过uv run执行。 - source 业务代码不直接解析 contract；contract 读取集中在
pipeline/contract_tools和相关 adapter。 - scheduler 允许
scheduler.defs.contract_schemas和scheduler.defs.clickhouse.specs作为 contract boundary 直接 importfleur_contracts。 - scheduler source business code 和
S3IOManager不直接 importfleur_contracts；运行时只 importscheduler.defs.contract_schemas暴露的 schema maps/constants。
常用入口
- 数据集契约：
pipeline/contracts/datasets/*.yml - 表 glossary：
pipeline/contracts/glossary/tables.yml - dbt canonical 字段 glossary：
pipeline/elt/metadata/field_glossary.yml - contract CLI：
pipeline/contract_tools/src/fleur_contracts/cli.py - 描述质量门禁：
pipeline/contract_tools/src/fleur_contracts/description_quality.py - Parquet adapter：
pipeline/contract_tools/src/fleur_contracts/adapters/parquet.py - Parquet adapter tests：
pipeline/contract_tools/tests/test_parquet_adapter.py - scheduler Parquet schema boundary：
pipeline/scheduler/src/scheduler/defs/contract_schemas.py - scheduler contract schema tests：
pipeline/scheduler/tests/unit/test_contract_schemas.py - data_dict 生成器：
pipeline/contract_tools/src/fleur_contracts/adapters/data_dict.py - dbt sources YAML 生成器：
pipeline/contract_tools/src/fleur_contracts/adapters/dbt.py
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 · 146 lines · 89 tokens per session scan A 9a78ebbb8821
fleur-contract-data-dictionary is a skill published in the GitHub repository WackyGem/Fleur (112 stars, last pushed 1mo ago), licensed MIT. It adds 89 tokens to every session and 2,013 once invoked, about $0.0004 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 skills, from other repositories
schema-exploration
Lists tables, describes columns and data types, identifies foreign key relationships, and maps entity relationships in a database. Use when the user asks about database schema, table structure, column types, what tables exist, ERD, foreign keys, or how entities relate.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
supabase
Supabase / PostgREST Row-Level-Security playbook — pull the anon (or leaked servicerole) key out of the frontend JS, map tables from the auto-generated OpenAPI spec, test anonymous RLS READ disclosures (PII/secret leaks), and anonymous RLS WRITE abuse (insert/update/delete — e.g. forging…
dsql
Build with Aurora DSQL — manage schemas, execute queries, handle migrations, diagnose query plans, diagnose cluster performance, load data, and develop applications with a serverless, distributed SQL database. Covers IAM auth, multi-tenant patterns, MySQL-to-DSQL and PostgreSQL-to-DSQL schema conversion, foreign key…
nw-ddd-eventsourcing
Event Sourcing and CQRS as DDD implementation patterns — when to use, aggregate event streams, projections, snapshots, sagas, upcasting, conflict resolution.
sql-translate
Translate SQL queries between database dialects (Snowflake, BigQuery, PostgreSQL, MySQL, etc.).