dbt-model-enhancement

dbt-model-enhancement is a skill for Claude Code from AltimateAI/data-engineering-skills. It costs 198 tokens per session (3,919 once invoked), scanned A, original, MIT.

A workflow for changing one existing dbt model from a ticket. dbt is a tool that builds SQL-based data models and checks them in a data warehouse.

In plain words
What is it for?
Use it to locate a model, apply a ticketed change, run dbt checks, review the result, and prepare a pull request.
Why use it?
It keeps a small requested change limited to one model and validates it before the change is proposed. It helps avoid accidentally changing production data by requiring a non-production target.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the dbt-skills plugin — 9 skills shipped together

Good fit Use it to locate a model, apply a ticketed change, run dbt checks, review the result, and prepare a pull request.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/altimateai/data-engineering-skills/dbt-model-enhancement
Install

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.

Any agent
npx skills add AltimateAI/data-engineering-skills --skill dbt-model-enhancement
Clone the repo
git clone --depth 1 https://github.com/AltimateAI/data-engineering-skills

Made for: Claude Code.

Or install dbt-skills, the plugin that ships this one along with the rest of its 9 skills.

Wrote 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.

agentmods badge for dbt-model-enhancement

README.md
[![agentmods](https://agentmods.dev/badge/skills/altimateai/data-engineering-skills/dbt-model-enhancement/github.svg)](https://agentmods.dev/skills/altimateai/data-engineering-skills/dbt-model-enhancement)
Your own site
<a href="https://agentmods.dev/skills/altimateai/data-engineering-skills/dbt-model-enhancement"><img src="https://agentmods.dev/badge/skills/altimateai/data-engineering-skills/dbt-model-enhancement/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.

agentmods 80×15 button for dbt-model-enhancement

Your own site · 80×15
<a href="https://agentmods.dev/skills/altimateai/data-engineering-skills/dbt-model-enhancement"><img src="https://agentmods.dev/badge/skills/altimateai/data-engineering-skills/dbt-model-enhancement.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 198 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,919 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00198 $0.03919
Opus 5.5 $0.00079 $0.01568
Sonnet 5.5 $0.00040 $0.00784
Haiku 4.5 $0.00020 $0.00392

Measured today against content hash 57b16d98639c, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

dbt-model-enhancement 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 today.

The scan reads SKILL.md. This mod also ships 2 executable files (scripts/prod_guard.sh, scripts/state.sh), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

skills/dbt/dbt-model-enhancement/SKILL.md · 383 lines

How it starts

The opening of the file, as written. The whole thing — 383 lines — stays where its author put it; the contents beside it link to each section on GitHub.

dbt-model-enhancement

Locate model → read ticket (as data) → change → validate → self-review → PR → summary.

When NOT to use this skill

  • Model doesn't exist yet → creating-dbt-models.
  • The change spans multiple models or needs CTE extraction / macro consolidation → refactoring-dbt-models.
  • The ticket asks to tune a slow query, not change the model's output → snowflake-query-optimization.
  • The ticket asks to migrate SQL from another engine → migrating-sql-to-dbt or mssql-to-snowflake-dbt-migration.

Prerequisites

Verify what's available before invoking — do not assume.

command -v dbt   # required
command -v gh    # required if PR creation is in scope
command -v git   # required
command -v altimate-code   # optional — nicer parity + diff

Must have:

  • A working dbt project (dbt_project.yml at the project root) with warehouse credentials configured in profiles.yml or env vars.
  • A non-prod dbt target (dev, ci, or any target whose profile does NOT write into the production schema). Phase 5's dbt build will refuse to run without one.
  • git + gh authenticated against the project's remote (gh auth status) if PR creation is expected.

Nice to have:

  • A JIRA/Linear/Atlassian MCP for ticket fetching. If not available, the skill falls back to GitHub issues via gh or asks the user to paste the ticket body.

If dbt or git is missing, stop and tell the user.

Time budget

Target end-to-end runtime: ≤6 min (360s), hard ceiling 8 min (480s). Per-phase caps (sum = 360s): Phase 1 ≤20s · Phase 2 ≤30s · Phase 3 ≤10s · Phase 4 ≤90s · Phase 5 ≤90s · Phase 6 ≤30s · Phase 7 ≤60s · Phase 8 ≤30s.

Inputs

  • Model: name, file path, or "the model" (resolve via find models -name "<name>.sql").
  • Change source: a JIRA / Linear / GitHub issue URL, OR inline instructions in the prompt.
  • Default base branch: main (confirm from git symbolic-ref refs/remotes/origin/HEAD if unsure).

Read the full file on GitHub · 383 lines

Files

What ships with it

2 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.

Changes

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.

  1. today First seen · 383 lines · 198 tokens per session scan A 57b16d98639c

Subscribe to this mod's changes

dbt-model-enhancement is a skill published in the GitHub repository AltimateAI/data-engineering-skills (130 stars, last pushed yesterday), licensed MIT. It adds 198 tokens to every session and 3,919 once invoked, about $0.0008 per session on Opus 5.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-10-28.

Related

Other skills, from other repositories

misata

Generate relational test, demo or evaluation data from a declared schema with Misata, where every declaration (foreign keys, unique and CHECK rules, monthly revenue curves, rates, group shares, ledger identities) holds exactly or is refused before generation, then attest the files. Use when a task needs a seeded…

rasinmuhammed/misata · 101 tokens

sql-architect

SQL standards — UUID v7 PKs, snakecase, soft delete, forward-only migrations, parameter binding, N+1 prevention, EXPLAIN-driven indexing. PostgreSQL 18 primary; MySQL 9 and SQLite 3.53 noted. Use when designing schemas, writing queries, or auditing a database layer.

ralvarezdev/ralvaskills · 69 tokens

backend-patterns

Backend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes.

Methasit-Pun/data_engineer_claude_skills · 31 tokens

dbt-patterns

The most important design decision in a dbt project is how to organize model layers. A clear layer structure means every model has exactly one place it belongs, and anyone reading the project can understand what each model does.

Methasit-Pun/data_engineer_claude_skills · 143 tokens

data-migration

Moving data between systems safely — cutover planning, backfill strategies, dual-write patterns, validation, rollback procedures, and zero-downtime migration techniques. Use this skill whenever the team is migrating from one database or warehouse to another (MySQL → Snowflake, Redshift → BigQuery, on-prem → cloud)…

Methasit-Pun/data_engineer_claude_skills · 160 tokens

schema-design

Data modeling for analytical workloads — star schema, snowflake schema, one big table (OBT), slowly changing dimensions (SCD), normalization tradeoffs, grain definition, and surrogate key strategies. Use this skill whenever the user is designing or reviewing a data warehouse schema, planning a fact/dimension table…

Methasit-Pun/data_engineer_claude_skills · 143 tokens