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 orchestra-hq/orchestra-skills --skill dbt-core-dagster-to-orchestragit clone --depth 1 https://github.com/orchestra-hq/orchestra-skillsWrote 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/orchestra-hq/orchestra-skills/dbt-core-dagster-to-orchestra)<a href="https://agentmods.dev/skills/orchestra-hq/orchestra-skills/dbt-core-dagster-to-orchestra"><img src="https://agentmods.dev/badge/skills/orchestra-hq/orchestra-skills/dbt-core-dagster-to-orchestra/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/orchestra-hq/orchestra-skills/dbt-core-dagster-to-orchestra"><img src="https://agentmods.dev/badge/skills/orchestra-hq/orchestra-skills/dbt-core-dagster-to-orchestra.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.00107 | $0.02091 |
| Opus 5 | $0.00053 | $0.01045 |
| Sonnet 5 | $0.00021 | $0.00418 |
| Haiku 4.5 | $0.00011 | $0.00209 |
Grade A, and why
dbt-core-dagster-to-orchestra 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.
How it starts
The opening of the file, as written. The whole thing — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
dbt Core: Dagster -> Orchestra Conversion
Overview
In Dagster, dbt Core is a flagship integration via dagster-dbt: a DbtCliResource runs the dbt CLI and @dbt_assets parses the dbt manifest.json to produce asset-level lineage. The decorated function streams dbt.cli([...]) commands.
In Orchestra, dbt Core is a first-class integration. A single Execute task under DBT_CORE replaces one or more @dbt_assets. Orchestra pulls the dbt project from a connected Git repository and runs the commands you specify.
Parameter Mapping
| Dagster concept | Orchestra YAML field | Notes |
|---|---|---|
dbt.cli(["build", "--select", ...]) |
parameters.commands |
Semicolon-separated dbt CLI string |
| Python environment | parameters.python_version |
e.g. '3.12' |
| pip / poetry / uv | parameters.package_manager |
PIP, POETRY, or UV — infer from visible project files (poetry.lock/pyproject.toml → POETRY, uv.lock → UV, requirements.txt/Pipfile → PIP). If none of that is visible, don't silently guess PIP — see Gotchas |
DbtProject(project_dir=...) (Git repo + project) |
connection: for the repo/credentials, parameters.project_dir for the path |
The connection stores the repo URL; project_dir is a real task parameter — set it to the same subdirectory value, null if the project is at the repo root |
--project-dir |
parameters.project_dir |
Same as above — carry the path over, don't drop it |
profiles_dir / profiles.yml |
Configured on the connection | Warehouse creds live on the connection |
--select / --exclude |
Include in commands |
e.g. dbt build --select models/marts |
--target |
Include in commands or on connection |
e.g. dbt run --target prod |
| asset key / op name | name: |
Human-readable task name |
Orchestra YAML Structure
version: v1
name: <pipeline-name>
pipeline:
<stage-uuid>:
tasks:
<task-uuid>:
integration: DBT_CORE
integration_job: DBT_CORE_EXECUTE
name: <descriptive name>
connection: <orchestra-dbt-core-connection-name>
parameters:
commands: 'dbt seed; dbt build --select tag:daily;'
package_manager: PIP
python_version: '3.12'
project_dir: null # optional — subdirectory holding dbt_project.yml, e.g. 'dbt' in a monorepo
depends_on: []
condition: null
tags: []
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.
- 12d ago First seen · 152 lines · 107 tokens per session scan A 09b1930f0367
dbt-core-dagster-to-orchestra is a skill published in the GitHub repository orchestra-hq/orchestra-skills (9 stars, last pushed 3d ago), licensed MIT. It adds 107 tokens to every session and 2,091 once invoked, about $0.0005 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.
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…
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.
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.
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…
training-check
Interactively monitor training metrics from the current Codex session, periodically checking WandB or fallback logs for NaN, divergence, plateaus, and broken runs.
nemo-automodel-launcher-config
Configure NeMo AutoModel job launches for interactive runs, Slurm clusters, and SkyPilot cloud execution.