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 vaquarkhan/data-engineering-agent-skills --skill unity-catalog-and-lakehouse-governancegit clone --depth 1 https://github.com/vaquarkhan/data-engineering-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/vaquarkhan/data-engineering-agent-skills/unity-catalog-and-lakehouse-governance)<a href="https://agentmods.dev/skills/vaquarkhan/data-engineering-agent-skills/unity-catalog-and-lakehouse-governance"><img src="https://agentmods.dev/badge/skills/vaquarkhan/data-engineering-agent-skills/unity-catalog-and-lakehouse-governance/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/vaquarkhan/data-engineering-agent-skills/unity-catalog-and-lakehouse-governance"><img src="https://agentmods.dev/badge/skills/vaquarkhan/data-engineering-agent-skills/unity-catalog-and-lakehouse-governance.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00061 | $0.00624 |
| Opus 5 | $0.00030 | $0.00312 |
| Sonnet 5 | $0.00012 | $0.00125 |
| Haiku 4.5 | $0.00006 | $0.00062 |
Grade A, and why
unity-catalog-and-lakehouse-governance 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.
How it starts
The opening of the file, as written. The whole thing — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Unity Catalog And Lakehouse Governance
Overview
Use this skill when Unity Catalog is the core governance surface for a Databricks platform. It helps agents design governed boundaries across catalogs, schemas, storage locations, shares, and access paths for lakehouse data products.
When to Use
- designing
Unity Cataloghierarchy and ownership - defining external locations, credentials, and storage boundaries
- governing shared
Deltatables, views, volumes, or models - reviewing cross-workspace or multi-team lakehouse governance
- planning secure sharing, publish approvals, or governed consumer access
Do not reduce Unity Catalog to permissions only. It is also a publish, ownership, and operating-boundary decision.
Workflow
-
Define the governance hierarchy. Decide:
- catalog boundaries
- schema boundaries
- producer versus consumer separation
- ownership and stewardship paths
-
Define storage and credential boundaries. Cover:
- external locations
- managed versus external tables
- storage credentials
- workspace and environment separation
-
Define access and sharing behavior. Include:
- roles and groups
- row or column restrictions where needed
- governed views
- cross-team or external sharing expectations
-
Align governance with lakehouse delivery. Require:
- clear publish layers
- lineage visibility
- certification or trust signals
- handling for schema and contract change
-
Validate day-2 operations. Review how promotions, new workspaces, external consumers, and object-store boundaries behave under the governance model.
Common Rationalizations
| Rationalization | Reality |
|---|---|
| "We already use Databricks, so Unity Catalog design is obvious." | Poor catalog and location design creates long-term friction in ownership, sharing, and environment boundaries. |
| "We can give broad workspace access and tighten later." | Over-broad access becomes hard to unwind once shared data products are adopted. |
| "Lineage comes for free." | Platform lineage is useful only when publish boundaries and ownership are designed intentionally. |
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.
- 9d ago First seen · 78 lines · 61 tokens per session scan A 3d7d846ad8c8
unity-catalog-and-lakehouse-governance is a skill published in the GitHub repository vaquarkhan/data-engineering-agent-skills (45 stars, last pushed 3mo ago), licensed MIT. It adds 61 tokens to every session and 624 once invoked, about $0.0003 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
cqrs-implementation
Implement Command Query Responsibility Segregation for scalable architectures. Use when separating read and write models, optimizing query performance, or building event-sourced systems.
projection-patterns
Build read models and projections from event streams. Use when implementing CQRS read sides, building materialized views, or optimizing query performance in event-sourced systems.
sl
Skill "sl" from Kaelio/ktx, covering semantic layer, part 1 - schema reference, overlay sources, standalone table sources and standalone sql sources.
historic_sql_table_digest
Convert one changed historic-SQL table usage bucket into typed table usage evidence for deterministic schema projection.
live_database_ingest
Capture semantic-layer and knowledge updates from a live database schema snapshot.
durable-objects
Build, debug, or review Cloudflare Durable Objects code for persistent state and coordination.