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 skills add j4flmao/agent-skills --skill data-lakehousegit clone --depth 1 https://github.com/j4flmao/agent-skillsWrote 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/j4flmao/agent-skills/data-lakehouse)<a href="https://agentmods.dev/skills/j4flmao/agent-skills/data-lakehouse"><img src="https://agentmods.dev/badge/skills/j4flmao/agent-skills/data-lakehouse/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.
<a href="https://agentmods.dev/skills/j4flmao/agent-skills/data-lakehouse"><img src="https://agentmods.dev/badge/skills/j4flmao/agent-skills/data-lakehouse.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00113 | $0.06696 |
| Opus 5 | $0.00056 | $0.03348 |
| Sonnet 5 | $0.00023 | $0.01339 |
| Haiku 4.5 | $0.00011 | $0.00670 |
Grade A, and why
data-data-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 6d 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 — 602 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Data Data Lakehouse
Purpose
Design lakehouse architectures that merge data lake flexibility with warehouse reliability. Implement medallion architecture for data quality progression, Unity Catalog for governance, Delta Sharing for data collaboration, and multi-cloud deployment patterns.
Agent Protocol
Trigger
Exact user phrases: "lakehouse", "medallion architecture", "bronze", "silver", "gold", "Databricks", "Unity Catalog", "Delta Sharing", "Apache Paimon", "multi-cloud lakehouse", "open formats", "lakehouse governance", "data mesh lakehouse".
Input Context
Before activating, verify:
- Cloud provider (AWS, Azure, GCP, multi-cloud)
- Lakehouse platform (Databricks, AWS EMR, Azure Synapse, GCP Dataproc)
- Table format (Delta, Iceberg, Paimon)
- Data sources volume and types
- Number of data producers and consumers
- Security requirements (RBAC, column mask, row filter)
- Data sharing requirements (internal teams, external partners)
Output Artifact
Lakehouse architecture with medallion layers, Unity Catalog configuration, and platform deployment specs.
Response Format
Lakehouse Platform: {Databricks | EMR + Iceberg | Synapse + Delta | Dataproc + Iceberg}
Catalog: {Unity Catalog | Hive Metastore | AWS Glue | Nessie}
Table Format: {Delta | Iceberg | Paimon}
Medallion Layers: Bronze (raw), Silver (cleaned), Gold (aggregated)
Sharing: {Delta Sharing | open | proprietary}
# Unity Catalog metastore config
# Medallion pipeline YAML
No preamble. No postamble. No explanations. No filler/hedging/transitions. Compress output — why use many token when few do trick.
Completion Criteria
- Medallion layers defined with data flow and transformations
- Unity Catalog or equivalent metastore configured
- RBAC and column-level security defined
- Delta Sharing setup for cross-team/partner data access
- Table format selected with interoperability plan
- Multi-cloud or cross-region replication strategy
- Data quality checks at each medallion layer
- Platform deployment topology (compute, storage, catalog)
What ships with it
26 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- references/api_reference.md 1.9 KB
- references/architecture_patterns.md 2.5 KB
- references/architecture-patterns.md 2.1 KB
- references/code-organization.md 1.9 KB
- references/configuration_guide.md 1.9 KB
- references/deployment_strategies.md 2.2 KB
- references/deployment-pipelines.md 2.4 KB
- references/error-handling.md 2.1 KB
- references/integration_guide.md 2.1 KB
- references/lakehouse-architecture-patterns.md 2.0 KB
- references/lakehouse-architecture.md 2.2 KB
- references/lakehouse-catalog-integration.md 2.3 KB
- references/lakehouse-ecosystem-tools.md 2.0 KB
- references/lakehouse-format-deep-dive.md 2.0 KB
- references/lakehouse-monitoring.md 1.9 KB
- references/lakehouse-performance-optimization.md 2.6 KB
- references/lakehouse-platform.md 1.9 KB
- references/lakehouse-query-engines.md 2.2 KB
- references/medallion-architecture.md 2.2 KB
- references/performance_tuning.md 2.1 KB
- references/performance-optimization.md 2.2 KB
- references/security_best_practices.md 2.5 KB
- references/security-best-practices.md 2.2 KB
- references/state-management.md 2.1 KB
- references/testing-strategies.md 2.1 KB
- references/troubleshooting_guide.md 2.2 KB
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.
- 6d ago First seen · 602 lines · 113 tokens per session scan A 78ab1424e27c
data-data-lakehouse is a skill published in the GitHub repository j4flmao/agent-skills (22 stars, last pushed 3d ago), licensed MIT. It adds 113 tokens to every session and 6,696 once invoked, about $0.0006 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-03.
Other skills, from other repositories
databricks-expert
Expert-level Databricks platform, Apache Spark, Delta Lake, MLflow, notebooks, and cluster management. Use when the user mentions Apache Spark, Delta Lake, MLflow, lakehouse architecture, or PySpark, or when the task involves Cluster Configuration and Management, Delta Lake Architecture, PySpark Data Processing, or…
architecture-diagram
Dark-themed SVG architecture/cloud/infra diagrams as HTML.
senior-data-engineer
World-class data engineering skill for building scalable data pipelines, ETL/ELT systems, real-time streaming, and data infrastructure. Expertise in Python, SQL, Spark, Airflow, dbt, Kafka, Flink, Kinesis, and modern data stack. Includes data modeling, pipeline orchestration, data quality, streaming quality…
aws-architecture-diagram
AWS architecture diagrams — generate visual network topology diagrams from live AWS infrastructure. Use when drawing AWS network diagrams, visualizing VPCs, mapping Transit Gateway topology, or generating architecture documentation.
architecture-paradigm-microservices
Applies microservices for independent deployment and per-service scaling. Use when teams need autonomous release cycles with distinct capability scaling needs.
architecture-paradigm-serverless
Applies serverless FaaS patterns for event-driven workloads. Use when designing bursty workloads with minimal infrastructure and pay-per-execution cost model.