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 mexmarv/ai-genie-factory --skill databricks-dashboardgit clone --depth 1 https://github.com/mexmarv/ai-genie-factoryWrote 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/mexmarv/ai-genie-factory/databricks-dashboard)<a href="https://agentmods.dev/skills/mexmarv/ai-genie-factory/databricks-dashboard"><img src="https://agentmods.dev/badge/skills/mexmarv/ai-genie-factory/databricks-dashboard/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/mexmarv/ai-genie-factory/databricks-dashboard"><img src="https://agentmods.dev/badge/skills/mexmarv/ai-genie-factory/databricks-dashboard.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.00146 | $0.08290 |
| Opus 5 | $0.00073 | $0.04145 |
| Sonnet 5 | $0.00029 | $0.01658 |
| Haiku 4.5 | $0.00015 | $0.00829 |
Grade A, and why
databricks-dashboard 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 11d 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 — 802 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Databricks AI/BI Dashboard Patterns — Alpura
Apply to every native Databricks Lakeview Dashboard. These run directly in the Databricks workspace — no Python app needed. Always read from Gold layer tables only.
Always load @databricks-dashboard-colors alongside this skill for the dashboard's dark/light theme tokens and visualization palette, set via the Lakeview Theme panel — not
@ui-ux-patterns, which covers Python/Plotly Apps. Follow the 60-30-10 rule for colors.For conversational / natural language interfaces on top of Gold tables, use Genie Spaces (managed via
manage_genieMCP tool) instead of, or alongside, Lakeview Dashboards.
Rules
- Datasets are SQL queries — always Gold layer (
prod.gold.*orsystem.*) - Every filter widget must use a named parameter — no hardcoded
WHEREclauses - Counter tiles show ONE metric with a comparison period
- Use dashboard-level filters, not per-tile filters, for date range and dimension slices
- Markdown tiles for section headers — never skip them in multi-section dashboards
- All SQL in datasets must be readable by the service principal running the refresh
- Never JOIN more than 3 tables in a single dataset — pre-join in Gold if needed
- Schedule refreshes for non-interactive dashboards — never leave manual-only for ops
Dataset SQL Patterns
Parameterized Date Filter
-- Dataset: daily_sales
-- Parameters: start_date (date), end_date (date), region (string, default='All')
SELECT
order_date,
region,
SUM(amount) AS total_sales,
COUNT(order_id) AS order_count,
AVG(amount) AS avg_order_value,
SUM(amount) / NULLIF(LAG(SUM(amount)) OVER (ORDER BY order_date), 0) - 1 AS wow_growth
FROM prod.gold.sales_daily
WHERE order_date BETWEEN :start_date AND :end_date
AND (:region = 'All' OR region = :region)
GROUP BY order_date, region
ORDER BY order_date
KPI Comparison Dataset (Current vs Prior Period)
-- Dataset: kpi_summary
-- Computes current period metrics alongside prior period for delta display
WITH current_period AS (
SELECT
SUM(amount) AS revenue,
COUNT(order_id) AS orders,
AVG(amount) AS avg_order,
COUNT(DISTINCT customer_id) AS unique_customers
FROM prod.gold.sales_daily
WHERE order_date BETWEEN :start_date AND :end_date
),
prior_period AS (
SELECT
SUM(amount) AS revenue_prior,
COUNT(order_id) AS orders_prior,
AVG(amount) AS avg_order_prior,
COUNT(DISTINCT customer_id) AS customers_prior
FROM prod.gold.sales_daily
WHERE order_date BETWEEN
DATEADD(day, -DATEDIFF(day, :start_date, :end_date) - 1, :start_date)
AND DATEADD(day, -1, :start_date)
)
SELECT
c.*,
p.*,
ROUND((c.revenue - p.revenue_prior) / NULLIF(p.revenue_prior, 0) * 100, 1) AS revenue_pct,
ROUND((c.orders - p.orders_prior) / NULLIF(p.orders_prior, 0) * 100, 1) AS orders_pct
FROM current_period c, prior_period p
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.
- 11d ago First seen · 802 lines · 146 tokens per session scan A 22af4b65f5b5
databricks-dashboard is a skill published in the GitHub repository mexmarv/ai-genie-factory (5 stars, last pushed 1mo ago), licensed MIT. It adds 146 tokens to every session and 8,290 once invoked, about $0.0007 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-31.
Other skills, from other repositories
data-divergence
Investigate why two datasets that should agree don't — two pipelines writing the same logical table, a rollup vs the detail it aggregates, a dashboard vs its source, one environment vs another. Use when row counts, totals, or date ranges disagree and the question is what happened rather than just what differs. Covers…
sql-diagram
Diagram a SQL query and explain what it shows — either its execution steps (mode=plan) or its column lineage (mode=lineage) — then trace it through small data so the defects the picture cannot show become visible. Use when asked to visualize, diagram, explain or review what a query does, how it joins its tables, or…
project-costs
Run the project cost report and write the analysis into it. Use when asked about this project's cloud spend, cost anomalies, spikes or trends, DBU/DSU consumption, per-job or per-pipeline cost, or the AWS vs Databricks split. Runs make project-costs (AWS Cost Explorer + Databricks system.billing), then analyses the…
agent-loop-safety
Wrap an agent loop with step limits, cost caps, human approval gates, and a full trace. Use whenever building or reviewing any tool-calling agent before it touches real systems.
agent-ops-handoff
Move an agent from laptop demo to operated system, tracing, cost dashboard, scheduled runs, alerting, and rollback. Use when an agent is about to run unattended or serve real users.
ai-output-review
Review AI-generated code or text before accepting it, spec diff, verifier run, secret scan, and the AI smell list. Use before merging any agent-produced change.