agentspec: Command for Claude Code

.claude/commands/data-engineering/lakehouse.md

lakehouse is a command for Claude Code from luanmorenommaciel/agentspec. It costs 16 tokens per session (352 once invoked), scanned A, original, MIT.

A command that gives guidance on lakehouses, systems for storing and analyzing large datasets in tables, including Iceberg and Delta Lake formats and data catalogs.

In plain words
What is it for?
Use it to design table definitions, partitioning, catalog settings, migrations, and compaction procedures.
Why use it?
It helps choose a table format and organize table storage, catalogs, migrations, and maintenance procedures.

Command for Claude Code

Written for Claude Code: installed under .claude/.

This is luanmorenommaciel/agentspec's own configuration. It tells Claude Code how to work on agentspec 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 agentspec configures →

Reuse

Borrowing it

Nothing to install: this file belongs to luanmorenommaciel/agentspec. 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/luanmorenommaciel/agentspec/main/.claude/commands/data-engineering/lakehouse.md
Clone the repo
git clone --depth 1 https://github.com/luanmorenommaciel/agentspec

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 lakehouse

README.md
[![agentmods](https://agentmods.dev/badge/commands/luanmorenommaciel/agentspec/lakehouse.svg)](https://agentmods.dev/commands/luanmorenommaciel/agentspec/lakehouse)
Your own site
<a href="https://agentmods.dev/commands/luanmorenommaciel/agentspec/lakehouse"><img src="https://agentmods.dev/badge/commands/luanmorenommaciel/agentspec/lakehouse.svg" alt="Measured on agentmods" height="20"></a>
Per session 16 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 352 The whole file, excluding the scripts and references it only reads on demand.
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.00016 $0.00352
Opus 5 $0.00008 $0.00176
Sonnet 5 $0.00003 $0.00070
Haiku 4.5 $0.00002 $0.00035

Measured 7d ago against content hash 2856482f0d74, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-08, from the pricing page.

Security

Grade A, and why

lakehouse 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 7d 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/commands/data-engineering/lakehouse.md · 55 lines

What it actually says

Lakehouse Command

Get guidance on Iceberg, Delta Lake, catalogs, and open table formats

Usage

/lakehouse <description-or-question>

Examples

/lakehouse "Set up Iceberg tables with partition evolution"
/lakehouse "Migrate from Hive to Iceberg on AWS"
/lakehouse "Compare Delta Lake vs Iceberg for our use case"
/lakehouse "Configure Unity Catalog for multi-cloud"

What This Command Does

  1. Invokes the lakehouse-architect agent
  2. Analyzes your table format or catalog requirements
  3. Loads KB patterns from lakehouse and cloud-platforms domains
  4. Generates:
    • Table DDL with partition strategies
    • Catalog configuration (Unity, Polaris, Nessie)
    • Migration scripts from legacy formats
    • Compaction and maintenance procedures

Agent Delegation

Agent Role
lakehouse-architect Primary — Iceberg, Delta, catalog governance
data-platform-engineer Escalation — when infra provisioning is needed
spark-engineer Escalation — when Spark read/write optimization is needed

KB Domains Used

  • lakehouse — Iceberg v3, Delta Lake, catalog wars, DuckLake
  • cloud-platforms — platform-specific Iceberg/Delta patterns
  • spark — Spark table format integration

Output

The agent generates table definitions, catalog configs, and operational runbooks for your lakehouse setup.

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. 7d ago First seen · 55 lines · 16 tokens per session scan A 2856482f0d74

Subscribe to this mod's changes

lakehouse is a command published in the GitHub repository luanmorenommaciel/agentspec (246 stars, last pushed today), licensed MIT. It adds 16 tokens to every session and 352 once invoked, about $0.0001 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-09-01.