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 Kilo-Org/kilo-marketplace --skill migrating-dbt-project-across-platformsgit clone --depth 1 https://github.com/Kilo-Org/kilo-marketplaceWrote 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/kilo-org/kilo-marketplace/migrating-dbt-project-across-platforms)<a href="https://agentmods.dev/skills/kilo-org/kilo-marketplace/migrating-dbt-project-across-platforms"><img src="https://agentmods.dev/badge/skills/kilo-org/kilo-marketplace/migrating-dbt-project-across-platforms/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/kilo-org/kilo-marketplace/migrating-dbt-project-across-platforms"><img src="https://agentmods.dev/badge/skills/kilo-org/kilo-marketplace/migrating-dbt-project-across-platforms.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.00061 | $0.03487 |
| Opus 5 | $0.00030 | $0.01743 |
| Sonnet 5 | $0.00012 | $0.00697 |
| Haiku 4.5 | $0.00006 | $0.00349 |
Grade C, and why
migrating-dbt-project-across-platforms scanned grade C with 1 finding 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 8d 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf target/ This is a copy
100% identical to migrating-dbt-project-across-platforms — 3 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 227 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Migrating a dbt Project Across Data Platforms
This skill guides migration of a dbt project from one data platform (source) to another (target) — for example, Snowflake to Databricks, or Databricks to Snowflake.
The core approach: dbt Fusion compiles SQL in real-time and produces rich, detailed error logs that tell you exactly what's wrong and where. We trust Fusion entirely for dialect conversion — no need to pre-document every SQL pattern difference. The workflow is: read Fusion's errors, fix them, recompile, repeat until done. Combined with dbt unit tests (generated on the source platform before migration), we prove both compilation correctness and data correctness on the target platform.
Success criteria: Migration is complete when:
dbtf compilefinishes with 0 errors and 0 warnings on the target platform- All unit tests pass on the target platform (
dbt test --select test_type:unit) - All models run successfully on the target platform (
dbtf run)
Validation cost: Use dbtf compile as the primary iteration gate — it's free (no warehouse queries) and catches both errors and warnings from static analysis. Only dbtf run and dbt test incur warehouse cost; run those only after compile is clean.
Contents
- Additional Resources — Reference docs for installation, unit tests, profile targets
- Migration Workflow — 7-step migration process with progress checklist
- Don't Do These Things — Critical guardrails
- Known Limitations & Gotchas — Fusion-specific and cross-platform caveats
Additional Resources
- Installing dbt Fusion — How to install and verify dbt Fusion
- Generating Unit Tests — How to generate unit tests on the source platform before migration
- Switching Targets — How to configure the dbt target for the destination platform and update sources
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.
- 8d ago First seen · 227 lines · 61 tokens per session scan C ef61506d25eb
migrating-dbt-project-across-platforms is a skill published in the GitHub repository Kilo-Org/kilo-marketplace (175 stars, last pushed 22d ago), licensed Apache-2.0. It adds 61 tokens to every session and 3,487 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). It is 100% identical to migrating-dbt-project-across-platforms, differing in 3 lines, and is treated as a copy.
Other skills, from other repositories
pinecone
Managed vector DB for production RAG and search.
data-engineer
Build scalable data pipelines, modern data warehouses, and real-time streaming architectures. Implements Apache Spark, dbt, Airflow, and cloud-native data platforms.
graphjin-env
Use when setting up a training or evaluation loop against a GraphJin agent environment — running the container, reading /health, driving episodes hosted or step-by-step or with your own agent over MCP, splitting train from eval, exporting trajectories, and deciding whether two rewards can be compared.
ingesting-into-data-lake
Import data into the AWS data lake from S3 files, local uploads, JDBC databases (Oracle, SQL Server, PostgreSQL, MySQL, RDS, Aurora), Amazon Redshift, Snowflake, BigQuery, DynamoDB, or existing Glue catalog tables (migration). Default target is S3 Tables; standard Iceberg on a general purpose bucket is supported where…
similarity-search-patterns
Implement efficient similarity search with vector databases. Use when building semantic search, implementing nearest neighbor queries, or optimizing retrieval performance.
nornicdb-qdrant-migration
Migrate from Qdrant to NornicDB end-to-end through NornicDB's Qdrant-compatible gRPC surface. Covers connection setup, collection→database mapping, point→node mapping, the vector-config and named-vector replication, point upsert in batches, count verification, and what (deliberately) does not transfer (snapshots, HNSW…