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 hicham-bab/dbt-legacy-migration-skills --skill migrating-coalesce-to-dbtgit clone --depth 1 https://github.com/hicham-bab/dbt-legacy-migration-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/hicham-bab/dbt-legacy-migration-skills/migrating-coalesce-to-dbt)<a href="https://agentmods.dev/skills/hicham-bab/dbt-legacy-migration-skills/migrating-coalesce-to-dbt"><img src="https://agentmods.dev/badge/skills/hicham-bab/dbt-legacy-migration-skills/migrating-coalesce-to-dbt/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/hicham-bab/dbt-legacy-migration-skills/migrating-coalesce-to-dbt"><img src="https://agentmods.dev/badge/skills/hicham-bab/dbt-legacy-migration-skills/migrating-coalesce-to-dbt.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.00129 | $0.03716 |
| Opus 5 | $0.00064 | $0.01858 |
| Sonnet 5 | $0.00026 | $0.00743 |
| Haiku 4.5 | $0.00013 | $0.00372 |
Grade A, and why
migrating-coalesce-to-dbt 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 — 264 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Migrating Coalesce to dbt
This skill migrates a Coalesce.io project into a governed dbt project — reproducing each node's SQL as dbt models, snapshots, and sources with tests, docs, and contracts, then proving parity against warehouse data.
Disambiguation: Coalesce here is Coalesce.io — the column-aware data transformation platform (Coalesce Automation Inc.) for Snowflake / Databricks / BigQuery — not the former dbt Labs "Coalesce" conference (now dbt Summit).
The core approach: Coalesce is a push-down SQL tool, like dbt — every node compiles to SQL that runs in the target warehouse, and lineage is column-level. That makes a Coalesce node map onto a dbt model almost 1:1 (arguably the closest fit of any source tool). We inventory every node, translate each using the node answer key, validate each output against the warehouse, and report coverage and cost.
Scope — what maps:
- Source nodes → dbt
sources(raw declarations). - All other nodes (Stage / Persistent Stage / Dimension / Fact / View) → dbt models/snapshots. These are the migratable units and the coverage denominator.
- Jobs (schedules) → a dbt job/schedule — out of model scope. Custom node types (UDNs) with bespoke templates → a dbt macro/materialization, or flag for review.
Success criteria: Migration is complete when:
dbt compilefinishes with 0 errors and 0 warnings- Every generated model builds (
dbt build) and its tests pass - Data parity is proven for each mart (row-for-row or aggregate baseline — see Step 5)
- ≥95% of the transformable nodes are migrated and validated, with the residual explicitly listed
Validation cost: dbt compile is the free iteration gate. Only dbt build, dbt test, and the
parity queries touch the warehouse — run those after compile is clean.
This skill shares its workflow with the legacy-to-dbt-migration-foundations skill; steps below
link into its references. Assume the migrator may be new to dbt — explain each dbt concept
(materializations, incremental, snapshots, contracts, Fusion) in plain language as it comes up
(foundations → dbt-concepts-explained.md), and explain the reason behind each choice.
What ships with it
3 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.
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 · 264 lines · 129 tokens per session scan A b1af170a8e22
migrating-coalesce-to-dbt is a skill published in the GitHub repository hicham-bab/dbt-legacy-migration-skills (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 129 tokens to every session and 3,716 once invoked, about $0.0006 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.