bauplan-skills: Instructions file for Claude Code

CLAUDE.md

bauplan-skills CLAUDE.md is an instructions file for Claude Code from BauplanLabs/bauplan-skills. It costs 1,661 tokens per session, scanned A, original, MIT.

A set of instructions for using Bauplan, a data lakehouse platform, alongside Git for code changes. It explains when to use Bauplan's command line tool or Python library and includes safety rules.

In plain words
What is it for?
Creating Git and Bauplan branches, testing data pipelines, materializing data changes, and following safe commit and review practices.
Why use it?
It keeps code work and data work on the correct branches, records changes clearly, and reduces the risk of changing shared data or code by mistake.

Instructions file for Claude Code

Written for Claude Code: the file is CLAUDE.md.

This is BauplanLabs/bauplan-skills's own configuration. It tells Claude Code how to work on bauplan-skills itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything bauplan-skills configures →

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/CLAUDE.md
Clone the repo
git clone --depth 1 https://github.com/BauplanLabs/bauplan-skills

Made for: Claude Code.

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.

agentmods badge for bauplan-skills CLAUDE.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/bauplanlabs/bauplan-skills/claude-md/github.svg)](https://agentmods.dev/instructions/bauplanlabs/bauplan-skills/claude-md)
Your own site
<a href="https://agentmods.dev/instructions/bauplanlabs/bauplan-skills/claude-md"><img src="https://agentmods.dev/badge/instructions/bauplanlabs/bauplan-skills/claude-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.

agentmods 80×15 button for bauplan-skills CLAUDE.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/bauplanlabs/bauplan-skills/claude-md"><img src="https://agentmods.dev/badge/instructions/bauplanlabs/bauplan-skills/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,661 This file is loaded in full into every session.
When invoked 1,661 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.01661 $0.01661
Opus 5 $0.00830 $0.00830
Sonnet 5 $0.00332 $0.00332
Haiku 4.5 $0.00166 $0.00166

Measured 9d ago against content hash 100edbce38f0, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

bauplan-skills CLAUDE.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 9d 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.

CLAUDE.md · 120 lines

How it starts

The opening of the file, as written. The whole thing — 120 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:

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

Hard safety rules (always)

  1. Never publish by writing directly on main. Use a Bauplan branch and merge to publish.
  2. Never import data directly into main.
  3. 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.
  4. 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.
  5. 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 · 120 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.

  1. 9d ago First seen · 120 lines · 1,661 tokens per session scan A 100edbce38f0

Subscribe to this mod's changes

bauplan-skills CLAUDE.md is an instructions file published in the GitHub repository BauplanLabs/bauplan-skills (16 stars, last pushed 6d ago), licensed MIT. It adds 1,661 tokens to every session, about $0.0083 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.

Related

Other instructions, from other repositories

next.js AGENTS.md

AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens

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.

openai/codex · 5,153 tokens

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

microsoft/vscode · 6,785 tokens

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

microsoft/vscode · 5,001 tokens

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.

langchain-ai/langchain · 4,469 tokens

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.

deepseek-ai/deepseek-harness · 3,735 tokens