agentmods.dev

upgrading-dbt-core

upgrading-dbt-core is a skill for Claude Code from dbt-labs/dbt-agent-skills. It costs 213 tokens per session (7,272 once invoked), scanned A, original, Apache-2.0.

A procedure for upgrading a dbt-core project to version 1.12, including projects on earlier 1.x versions. dbt-core is the open-source software used to define and run data transformations.

In plain words
What is it for?
Migrating dbt-core versions, applying documented fixes through version 1.8, and setting only the behavior flags needed after version 1.8.
Why use it?
It handles breaking changes step by step and preserves existing behavior where newer versions changed how the project works.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter.

Part of the dbt-migration plugin — 3 skills shipped together

not rated 709repo +9 changed today A scan SkillSpector: warn 213 tokens original Apache-2.0

Good fit Migrating dbt-core versions, applying documented fixes through version 1.8, and setting only the behavior flags needed after version 1.8.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/dbt-labs/dbt-agent-skills/upgrading-dbt-core
View source ↗ dbt-labs/dbt-agent-skills
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 dbt-labs/dbt-agent-skills --skill upgrading-dbt-core
Clone the repo
git clone --depth 1 https://github.com/dbt-labs/dbt-agent-skills

Made for: Claude Code.

Or install dbt-migration, the plugin that ships this one along with the rest of its 3 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 upgrading-dbt-core

README.md
[![agentmods](https://agentmods.dev/badge/skills/dbt-labs/dbt-agent-skills/upgrading-dbt-core/github.svg)](https://agentmods.dev/skills/dbt-labs/dbt-agent-skills/upgrading-dbt-core)
Your own site
<a href="https://agentmods.dev/skills/dbt-labs/dbt-agent-skills/upgrading-dbt-core"><img src="https://agentmods.dev/badge/skills/dbt-labs/dbt-agent-skills/upgrading-dbt-core/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 upgrading-dbt-core

Your own site · 80×15
<a href="https://agentmods.dev/skills/dbt-labs/dbt-agent-skills/upgrading-dbt-core"><img src="https://agentmods.dev/badge/skills/dbt-labs/dbt-agent-skills/upgrading-dbt-core.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 213 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 7,272 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. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 1 finding, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium Excessive Agency · line 141
    Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
    Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
How audits are shown
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.00213 $0.07272
Opus 5 $0.00106 $0.03636
Sonnet 5 $0.00043 $0.01454
Haiku 4.5 $0.00021 $0.00727

Measured today against content hash 947148cd96ec, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

upgrading-dbt-core 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.

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-migration/skills/upgrading-dbt-core/SKILL.md · 548 lines

How it starts

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

Migrate a dbt project to dbt-core 1.12

You upgrade a dbt-core v1 project all the way to 1.12 — not one minor bump. Two different mechanisms apply, and you must not confuse them:

  • Up to 1.8 — genuinely breaking changes with no compatibility shim. You replay every version boundary in order from the project's current version, because consistent changelogs exist only per single minor version.

  • After 1.8 — every backwards-incompatible change ships gated behind a behavior-change flag in dbt_project.yml flags:. You do not fix those behaviors. Instead, for each such change the project actually exhibits, you pin its gating flag to false so the project keeps its current semantics and parses on 1.12. Several of these flags already default to true in 1.12, so for an affected project leaving the flag unset silently adopts the new behavior — pinning is what makes the migration behavior-preserving.

    Pin only what applies: a flag for a behavior the project does not use is dead config that hides the ones that matter. Detection per issue decides.

This skill is data-driven. The issues to resolve are not listed here — they arrive as a precompiled bundle, references/kb_<FROM>_<ADAPTER>.json, colocated with this SKILL.md. One bundle per starting version × adapter, each self-contained: every issue carries its own action, automation_type, and context.detection / context.fixing. Read the bundle; never fabricate an issue or a fix from memory.

The kb/ YAML corpus is the source those bundles are compiled from, at build time, by CI. It is not read during a migration and does not ship in the package. Never try to read it at runtime — work from the bundle.

Each issue has an automation_type that decides how it is handled:

automation_type How you handle it
deterministic dbt-autofix handles it. You do not re-implement it — you run the autofix operation, then map its diff onto the issue and record it.
agentic You apply the fix directly (per context.fixing), then verify.
human You propose the fix, show the diff, confirm with the user, then apply (HITL). Never apply a human issue without explicit confirmation.
behavior_flag The set-flag operation handles it, only when detection found it present (Step 5). A post-1.8 change gated behind a flag: when the project actually exhibits the gated behavior, the flag named in the issue's behavior_flag.name is pinned to false in dbt_project.yml. Never pin one the project does not exhibit, and never "fix" the underlying behavior instead.

Two orthogonal flags modify handling regardless of automation_type:

  • out_of_repo_risk: true — the fix may reach outside the repo (job --select, selectors.yml, BI tools, mesh refs). Record it for the user; you cannot complete it from the repo alone.
  • environment_change: true — dependency / Python-runtime / profiles change. Make an advisory edit only (e.g. note the requirements.txt/profiles.yml change); never execute pip/installers, and exclude it from the parse gate.

Read the full file on GitHub · 548 lines

Files

What ships with it

60 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 Changed 947148cd96ec
  2. 12d ago First seen · 548 lines · 213 tokens per session scan A 0bce4a7b0ee1

Subscribe to this mod's changes

upgrading-dbt-core is a skill published in the GitHub repository dbt-labs/dbt-agent-skills (709 stars, last pushed today), licensed Apache-2.0. It adds 213 tokens to every session and 7,272 once invoked, about $0.0011 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-30.

Data and AI
Related

Other skills, from other repositories

agent-platform-rag-engine-management

Manage and query Agent Platform RAG Engine Corpora and retrieve grounded contexts using the Google GenAI SDK. Use when listing RAG corpora or files, inspecting a corpus, retrieving contexts, or generating content grounded in a RAG corpus. Do not use for standard database queries (use SQL/Spanner skills), Google…

google/skills · 85 tokens

agent-platform-model-registry

Agent Platform Model Registry Management. Use when you need to upload, list, describe, update, or delete machine learning models (and their versions) in the Agent Platform Model Registry. Don't use for model training, model deployment to endpoints, or managing non-Agent Platform models.

google/skills · 60 tokens

foundry-config-setup

Resolve missing setup caused by a hardcoded Foundry project endpoint or model in a sample. Use when a sample fails because it uses a placeholder/hardcoded projectendpoint (for example "https://your-project.services.ai.azure.com") or a hardcoded model instead of reading them from the environment.

microsoft/agent-framework · 65 tokens

google-cloud-solution-agentic-analytics-spark-knowledge-catalog

Discovers requirements and generates guidance to design and deploy a governed, secure agentic-analytics solution for data that's distributed across Google Cloud, other cloud providers, or on-premises. Data that's outside Google Cloud (such as data from Databricks, Snowflake, Salesforce, SAP, or Oracle systems) is…

google/skills · 138 tokens

training-check

Interactively monitor training metrics from the current Codex session, periodically checking WandB or fallback logs for NaN, divergence, plateaus, and broken runs.

wanshuiyin/Auto-claude-code-research-in-sleep · 35 tokens

nemo-automodel-launcher-config

Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.

NVIDIA/skills · 30 tokens