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 Kilo-Org/kilo-marketplace --skill building-dbt-semantic-layergit clone --depth 1 https://github.com/Kilo-Org/kilo-marketplaceWrote 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/kilo-org/kilo-marketplace/building-dbt-semantic-layer)<a href="https://agentmods.dev/skills/kilo-org/kilo-marketplace/building-dbt-semantic-layer"><img src="https://agentmods.dev/badge/skills/kilo-org/kilo-marketplace/building-dbt-semantic-layer/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/kilo-org/kilo-marketplace/building-dbt-semantic-layer"><img src="https://agentmods.dev/badge/skills/kilo-org/kilo-marketplace/building-dbt-semantic-layer.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.00062 | $0.02119 |
| Opus 5 | $0.00031 | $0.01059 |
| Sonnet 5 | $0.00012 | $0.00424 |
| Haiku 4.5 | $0.00006 | $0.00212 |
Grade A, and why
building-dbt-semantic-layer 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.
This is a copy
97% identical to building-dbt-semantic-layer — 64 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Building the dbt Semantic Layer
This skill guides the creation and modification of dbt Semantic Layer components: semantic models, entities, dimensions, and metrics.
- Semantic models - Metadata configurations that define how dbt models map to business concepts
- Entities - Keys that identify the grain of your data and enable joins between semantic models
- Dimensions - Attributes used to filter or group metrics (categorical or time-based)
- Metrics - Business calculations defined on top of semantic models (e.g., revenue, order count)
Additional Resources
- Time Spine Setup - Required for time-based metrics and aggregations
- Best Practices - Design patterns and recommendations for semantic models and metrics
- Latest Spec Authoring Guide - Full YAML reference for dbt Core 1.12+ and Fusion
- Legacy Spec Authoring Guide - Full YAML reference for dbt Core 1.6-1.11
Determine Which Spec to Use
There are two versions of the Semantic Layer YAML spec:
- Latest spec - Semantic models are configured as metadata on dbt models. Simpler authoring. Supported by dbt Core 1.12+ and Fusion.
- Legacy spec - Semantic models are defined as separate top-level resources. Uses measures as building blocks for metrics. Supported by dbt Core 1.6 through 1.11. Also supported by Core 1.12+ for backwards compatibility.
Step 1: Check for Existing Semantic Layer Config
Look for existing semantic layer configuration in the project:
- Top-level
semantic_models:key in YAML files → legacy spec semantic_model:block nested under a model → latest spec
Step 2: Route Based on What You Found
If semantic layer already exists:
- Determine which spec is currently in use (legacy or latest)
- Check dbt version for compatibility:
- Legacy spec + Core 1.6-1.11 → Compatible. Use legacy spec guide.
- Legacy spec + Core 1.12+ or Fusion → Compatible, but offer to upgrade first using
uvx dbt-autofix deprecations --semantic-layeror the migration guide. They don't have to upgrade; continuing with legacy is fine. - Latest spec + Core 1.12+ or Fusion → Compatible. Use latest spec guide.
- Latest spec + Core <1.12 → Incompatible. Help them upgrade to dbt Core 1.12+.
What ships with it
4 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.
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.
- 7d ago First seen · 184 lines · 62 tokens per session scan A 85772b075714
building-dbt-semantic-layer is a skill published in the GitHub repository Kilo-Org/kilo-marketplace (175 stars, last pushed 21d ago), licensed Apache-2.0. It adds 62 tokens to every session and 2,119 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to building-dbt-semantic-layer, differing in 64 lines, and is treated as a copy.
Other skills, from other repositories
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for prisma-next. Use when the user wants to create a pull request, open a PR, or submit changes for review.
schema-exploration
Lists tables, describes columns and data types, identifies foreign key relationships, and maps entity relationships in a database. Use when the user asks about database schema, table structure, column types, what tables exist, ERD, foreign keys, or how entities relate.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
supabase
Supabase / PostgREST Row-Level-Security playbook — pull the anon (or leaked servicerole) key out of the frontend JS, map tables from the auto-generated OpenAPI spec, test anonymous RLS READ disclosures (PII/secret leaks), and anonymous RLS WRITE abuse (insert/update/delete — e.g. forging…
nornicdb-cypher-queries
Pick fast, predictable Cypher query shapes in NornicDB — point lookups, batch retrieval, pagination, search, traversal, batched UNWIND/MERGE writes, cleanup, multi-tenant isolation. Use when writing or reviewing Cypher whose latency or throughput matters; maps user intent to the executor's hot-path query templates.
dsql
Build with Aurora DSQL — manage schemas, execute queries, handle migrations, diagnose query plans, diagnose cluster performance, load data, and develop applications with a serverless, distributed SQL database. Covers IAM auth, multi-tenant patterns, MySQL-to-DSQL and PostgreSQL-to-DSQL schema conversion, foreign key…