agentmods.dev

configure-dbt-build-after

configure-dbt-build-after is a skill for Claude Code from orchestra-hq/orchestra-skills. It costs 219 tokens per session (1,564 once invoked), scanned A, original, MIT.

A configuration tool for dbt, a framework for building data models with SQL. It adds rules that make Orchestra rebuild a model only after a waiting period and when its upstream data is fresh.

In plain words
What is it for?
Use it to set per-model rebuild intervals in dbt model YAML or `dbt_project.yml`, and to enable Orchestra state-aware orchestration. It changes configuration but does not run dbt or start pipelines.
Why use it?
It prevents unnecessary model rebuilds when source data has not changed and helps coordinate rebuild timing with data freshness requirements.

Skill for Claude Code

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

Part of the orchestra plugin — 18 skills, 1 hook shipped together

not rated 9repo 3d ago A scan 219 tokens original MIT

Good fit Use it to set per-model rebuild intervals in dbt model YAML or dbt_project.yml, and to enable Orchestra state-aware orchestration. It changes configuration but does not run dbt or start pipelines.

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

Made for: Claude Code.

Or install orchestra, the plugin that ships this one along with the rest of its 18 skills, 1 hook.

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 configure-dbt-build-after

README.md
[![agentmods](https://agentmods.dev/badge/skills/orchestra-hq/orchestra-skills/configure-dbt-build-after/github.svg)](https://agentmods.dev/skills/orchestra-hq/orchestra-skills/configure-dbt-build-after)
Your own site
<a href="https://agentmods.dev/skills/orchestra-hq/orchestra-skills/configure-dbt-build-after"><img src="https://agentmods.dev/badge/skills/orchestra-hq/orchestra-skills/configure-dbt-build-after/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 configure-dbt-build-after

Your own site · 80×15
<a href="https://agentmods.dev/skills/orchestra-hq/orchestra-skills/configure-dbt-build-after"><img src="https://agentmods.dev/badge/skills/orchestra-hq/orchestra-skills/configure-dbt-build-after.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 219 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,564 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.00219 $0.01564
Opus 5 $0.00110 $0.00782
Sonnet 5 $0.00044 $0.00313
Haiku 4.5 $0.00022 $0.00156

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

Security

Grade A, and why

configure-dbt-build-after 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 12d 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.

skills/orchestra/skills/configure-dbt-build-after/SKILL.md · 95 lines

How it starts

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

Configure dbt build_after

Author the per-model build_after config so Orchestra rebuilds a model only when both its SLA window has elapsed and its upstream data is fresh. This is the model-side half of state-aware orchestration (SAO); the source-side half is source freshness (see the configure-dbt-source-freshness skill). This skill writes config only — it does not run dbt or trigger pipelines.

Unlike freshness, build_after is warehouse-agnostic — the same config works on Snowflake, BigQuery, Databricks, and MotherDuck. The only warehouse nuance lives upstream in the freshness signal it consumes.

When to use

  • User wants per-model rebuild SLAs, or to stop rebuilding models when nothing upstream changed.
  • User is setting up Orchestra SAO and needs the model-side gating.
  • Files like a model's YAML config: block or dbt_project.yml models: are in play.

What "done" looks like

  1. config.freshness.build_after (count, period, optional updates_on) is set on the target models, in the model YAML or dbt_project.yml, matching project conventions.
  2. use_state_orchestration: true is set on the Orchestra dbt Core task.
  3. Source freshness is confirmed present upstream (or flagged as a required companion step).
  4. A handoff explains the SLA values chosen, the updates_on choice, and how to verify.

Read first

  • ../../references/orchestra/dbt-sao/build-after.md — build_after schema and how to pick count/period/updates_on.
  • ../../references/orchestra/dbt-sao/orchestra-task.md — enabling SAO on the task.
  • ../../references/orchestra/dbt-sao/source-freshness.md — only if you also need to add the upstream freshness build_after depends on.

Workflow

  1. Confirm upstream freshness exists. build_after gates on "is upstream fresh?", which is meaningless without source freshness configured. Check the project's sources: YAML. If freshness is missing, say so and pair this with configure-dbt-source-freshness — don't author build_after against a signal that doesn't exist.

Read the full file on GitHub · 95 lines

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. 12d ago First seen · 95 lines · 219 tokens per session scan A ba4bd2d77d3b

Subscribe to this mod's changes

configure-dbt-build-after is a skill published in the GitHub repository orchestra-hq/orchestra-skills (9 stars, last pushed 3d ago), licensed MIT. It adds 219 tokens to every session and 1,564 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-31.

Analytics and metrics
Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens