What is bauplan-skills AGENTS.md?

A set of repository instructions for projects using Bauplan, a data lakehouse platform, and Git. It describes branch, commit, testing, and data-pipeline practices, including the distinction between Git branches and Bauplan data branches.

Use it to guide work on Bauplan data pipelines and their code repository, including creating branches, running dry runs, materializing data, and making focused commits.

It gives coding agents consistent rules for making changes without editing the main branch directly. It also prevents source-code workflow from being confused with Bauplan's versioned data workflow.

How BauplanLabs/bauplan-skills configures Codex and OpenCode

Reuse

Borrowing it

Nothing to install: this file belongs to BauplanLabs/bauplan-skills. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/BauplanLabs/bauplan-skills/main/AGENTS.md

Clone the repo

git clone --depth 1 https://github.com/BauplanLabs/bauplan-skills

Made for: Codex, OpenCode.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/bauplanlabs/bauplan-skills/agents-md/github.svg)](https://agentmods.dev/instructions/bauplanlabs/bauplan-skills/agents-md)

Your own site

<a href="https://agentmods.dev/instructions/bauplanlabs/bauplan-skills/agents-md"><img src="https://agentmods.dev/badge/instructions/bauplanlabs/bauplan-skills/agents-md/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/bauplanlabs/bauplan-skills/agents-md"><img src="https://agentmods.dev/badge/instructions/bauplanlabs/bauplan-skills/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 2,091 This file is loaded in full into every session.

When invoked 2,091 The same file — it is already loaded in full.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.02091	$0.02091
Opus 5.5	$0.00836	$0.00836
Sonnet 5.5	$0.00418	$0.00418
Haiku 4.5	$0.00209	$0.00209

Measured 1mo ago against content hash bace76b6da3c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

bauplan-skills 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 1mo 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.

AGENTS.md · 133 lines

How it starts

The opening of the file, as written. The whole thing — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Bauplan

Git Workflow (code repo)

This section is about git branches for source code, not Bauplan data branches.

Always create a new git branch before making any changes. Use a descriptive branch name based on the task (e.g., fix/login-bug, feat/add-search).
All work happens on feature branches. The main branch is off-limits for direct edits.
Commit every change immediately after making it. Each commit should have a clear, one-line message describing what changed.
Keep commits small and focused. One logical change per commit.
When the task is complete, leave the branch ready for review. Do not merge into main.

Bauplan Workflow (data lakehouse)

Bauplan is a data lakehouse platform where data changes follow a Git-like workflow, but on Bauplan data branches (managed by bauplan branch), not git branches. A typical workflow looks like this:

Create and switch to a new data branch: bauplan checkout -b <branch> --from-ref main
Iterate on your pipeline code and test with bauplan run --dry-run
When ready, run bauplan run to materialize — the code is snapshotted by Bauplan and saved under the jobId the platform returns
Review changes with bauplan branch diff main
Merge into main to publish

Hard safety rules (always)

Never publish by writing directly on main. Use a Bauplan branch and merge to publish.
Never import data directly into main.
Before merging into main, run bauplan branch diff main and review changes, or use bauplan query over the two branches to quickly compare how data changes in the target tables.
Prefer bauplan run --dry-run during iteration because it is much faster and safer. However, tables will not be materialized in the lake during a dry run, so the only way to preview table content is to use --preview (e.g., bauplan run --dry-run --preview head). Materialization is blocked on main. Every branch is readable, but only branches prefixed with your username (username.branchname) are writable by you.
When handling external API keys (LLM keys), do not hardcode them in code or commit them. Use Bauplan parameters or secrets.

Read the full file on GitHub · 133 lines

Changes

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.

1mo ago First seen · 133 lines · 2,091 tokens per session scan A bace76b6da3c

Subscribe to this mod's changes

bauplan-skills AGENTS.md is an instructions file published in the GitHub repository BauplanLabs/bauplan-skills (17 stars, last pushed 3d ago), licensed MIT. It adds 2,091 tokens to every session, about $0.0084 per session on Opus 5.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-09-25.

Data and AI Git and workflow

bauplan-skills AGENTS.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
bauplan-skills AGENTS.mdBauplanLabs/bauplan-skills	Instructions file	17	3d ago	MIT	A	2,091	Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	yesterday	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

bauplan-skills: Instructions file for Codex