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/malon64/openlakeforge/agents-mdgit clone --depth 1 https://github.com/malon64/openlakeforgeWhat 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.02648 | $0.02648 |
| Opus 5 | $0.01324 | $0.01324 |
| Sonnet 5 | $0.00530 | $0.00530 |
| Haiku 4.5 | $0.00265 | $0.00265 |
Grade A, and why
openlakeforge 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 — 209 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agent and contributor guide
This is the working guide for anyone changing OpenLakeForge — human or coding agent. It records what the repository actually enforces today. If a statement here disagrees with the code, the code wins and this file is a bug.
CLAUDE.md points here. There is one copy of these rules on purpose.
What this project is
OpenLakeForge is a cloud-agnostic, self-hostable lakehouse platform: open-source components assembled on Kubernetes with Terraform and Helm. The data path is CSV → Bronze → Floe validation → Silver Iceberg through Polaris → dbt-trino Gold → Trino → Superset, orchestrated by Dagster.
The audience is small data teams self-hosting a complete lakehouse. Runtime
footprint, onboarding friction, and recoverability are product features here,
not polish — a team without a platform engineer cannot absorb a stack that needs
one. v0.2-alpha is scoped around exactly that; see the roadmap.
Orientation — read in this order
README.md— stack, deployment targets, local workflowdocs/industrialization-roadmap.md— milestones, release gates, what is delivered and what is notdocs/architecture/overview.mdanddocs/architecture/provider-contracts.mddocs/adr/README.md— the decision log index; each ADR describes what binds today, all worth readingdocs/technical-debt.md— the live debt register with a fix path per itemdocs/architecture/diagrams/README.md— pod census and runtime topology
Current work is tracked in GitHub milestones. Issues carry priority: P0/P1/P2
labels expressing intended sequence within a milestone.
Repository map
| Path | Contains |
|---|---|
lakehouse_code/bronze/<source>/ |
Source-owned: source.yaml descriptor plus dlt extract |
lakehouse_code/silver/<domain>/ |
Domain-owned: Floe contracts and transformations |
lakehouse_code/gold/<product>/ |
Product-owned: dbt project |
lakehouse_code/dashboards/superset/<dashboard>/ |
Consumption-owned: Superset reports |
lakehouse_code/pipelines/dagster/ |
User-maintained Dagster orchestration code |
lakehouse_code/lakehouse.yaml |
Canonical domain/product business metadata descriptor |
openlakeforge.yaml |
Project-root Deployment Profile v1; parsed and resolved by olf profile validate/resolve (ADR 0011) |
libs/ |
Shared runtime Python imported by the project-code image |
packages/domain-model/ |
Canonical provider-neutral descriptor and inventory package |
tools/olf/ |
The olf CLI — uv-managed deploy tooling, contracts, artifacts, scaffolding, e2e |
infra/terraform/environments/ |
Per-environment wiring; contracts.tf is the contract surface |
infra/terraform/foundations/ |
Cluster and registry creation (kind, AKS, EKS) |
infra/terraform/modules/ |
Component modules grouped by capability |
infra/helm/values/local/ |
Helm values for the local profile |
images/project-code/ |
The Dagster runtime image |
release/component-catalog.yaml |
Immutable version, digest pins, and the distribution version contract both pyproject.toml files must match |
docs/schema/lakehouse.schema.json, docs/schema/source.schema.json |
Schemas lakehouse.yaml and source.yaml validate against |
docs/schema/deployment-profile.schema.json |
Schema openlakeforge.yaml validates against |
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 · 209 lines · 2,648 tokens per session scan A a8d23d75b067
openlakeforge AGENTS.md is an instructions file published in the GitHub repository malon64/openlakeforge (22 stars, last pushed 2d ago), licensed Apache-2.0. It adds 2,648 tokens to every session, about $0.0132 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
appwrite AGENTS.md
AGENTS.md instructions for appwrite/appwrite, covering appwrite, commands, stack, layout and libraries.
selfhost-ai CLAUDE.md
Instructions for kossakovsky/selfhost-ai, covering claude.md, project overview, core architecture, key files and installation flow.
infra CLAUDE.md
Instructions for anthr76/infra, covering claude.md, repository overview, development environment, common commands and task automation.
kubevirt-tekton-tasks AGENTS.md
Instructions for kubevirt/kubevirt-tekton-tasks, covering kubevirt tekton tasks - project guide, jira task management, documentation, project structure and key relationships.
docker-zoneminder CLAUDE.md
Instructions for jantman/docker-zoneminder, covering claude.md, project overview, build and test, ci/cd and architecture.
mitos CLAUDE.md
Instructions for mitos-run/mitos, covering claude.md, project overview, operating principles, commands and architecture.