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 agentmods add rules/hamzaamjad/cursor-rules/210-dbt-semantic-modelinggit clone --depth 1 https://github.com/hamzaamjad/cursor-rulesWrote 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/rules/hamzaamjad/cursor-rules/210-dbt-semantic-modeling)<a href="https://agentmods.dev/rules/hamzaamjad/cursor-rules/210-dbt-semantic-modeling"><img src="https://agentmods.dev/badge/rules/hamzaamjad/cursor-rules/210-dbt-semantic-modeling.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00567 |
| Opus 5 | $0.00000 | $0.00283 |
| Sonnet 5 | $0.00000 | $0.00113 |
| Haiku 4.5 | $0.00000 | $0.00057 |
Grade A, and why
210-dbt-semantic-modeling 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 3d 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.
What it actually says
dbt-semantic-modeling
Purpose: Build a consistent, governed, and reusable semantic layer using dbt's native semantic models.
1. Semantic Model Definition
- Define
semantic_models:in YAML undermodels/semantic/or a top-levelsemantic/folder. - Use singular, business-centric names (e.g.,
customers,orders). - Include
label,description, andmeta.ownerfor each model.
2. Dimensions & Hierarchies
- Under each model, list
dimensions:withname,type(e.g., primary_key, time, categorical), anddescription. - Define time hierarchies (
date,week,month) and business hierarchies (e.g., region → country → city).
3. Measures & Metrics
- Define
measures:withname,calculation_method(sum,average,derived),expression,timestamp,time_grains, andfilters. - Add
meta.business_definitionandvalidation_thresholdsfor quality checks. - Centralize metric definitions to ensure consistency across reports.
4. Relationships & Joins
- Declare
joins:at project level: specifyfrom,to,on, andrelationship(one_to_many, many_to_one). - Validate cardinality to prevent aggregation errors.
5. Exposures & Packages
- Use
exposures:to link semantic models to BI dashboards, notebooks, or APIs. - Leverage
exports:to share metrics and semantic definitions across projects.
6. Testing & Validation
- Write schema tests for semantic models: existence, types, and sample values.
- Implement custom SQL tests to validate key metrics against known benchmarks.
7. Documentation & Lineage
- Generate docs with
dbt docs generateincluding semantic models. - Tag models and measures for grouping (e.g.,
finance,marketing). - Version docs in CI; fail on outdated or missing metadata.
8. CI/CD & Governance
- Add semantic builds in CI (
dbt build --select semantic_models); fail on warnings/errors. - Enforce naming and style conventions via pre-commit hooks.
- Store governance metadata (
meta.access,tags.sensitivity) for row-level and column-level security.
9. Reusability & Parameterization
- Publish semantic layers as packages for reuse across teams.
- Parameterize definitions using
varsfor environment-specific overrides.
References: dbt Labs (Semantic Layer docs), knowledge_base/data_modeling/semantic/semantic_modeling_principles.md
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.
- 3d ago First seen · 49 lines · 0 tokens per session scan A dd8fadd0a4a1
210-dbt-semantic-modeling is a cursor rule published in the GitHub repository hamzaamjad/cursor-rules (2 stars, last pushed 1y ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 567 tokens. 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 cursor rules, from other repositories
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.
family-instance-domain-actions
Family instance domain action implementation patterns.