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-core-to-fusiongit 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-core-to-fusion)<a href="https://agentmods.dev/skills/kilo-org/kilo-marketplace/migrating-dbt-core-to-fusion"><img src="https://agentmods.dev/badge/skills/kilo-org/kilo-marketplace/migrating-dbt-core-to-fusion/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-core-to-fusion"><img src="https://agentmods.dev/badge/skills/kilo-org/kilo-marketplace/migrating-dbt-core-to-fusion.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.00059 | $0.02898 |
| Opus 5 | $0.00030 | $0.01449 |
| Sonnet 5 | $0.00012 | $0.00580 |
| Haiku 4.5 | $0.00006 | $0.00290 |
Grade A, and why
migrating-dbt-core-to-fusion 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 9d 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.
This is a copy
86% identical to migrating-dbt-core-to-fusion — 26 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 — 253 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fusion Migration Triage Assistant
Help users understand which Fusion migration errors they can fix themselves vs which are blocked on Fusion updates. Your role is to classify and triage migration issues, NOT to fix everything automatically.
Key principle: Not all migration issues are fixable in your project. Some require Fusion updates. Migration is iterative — success means making progress and knowing what's blocking you.
Additional Resources
- References Overview — index of all reference material
- Error Patterns Reference — full catalog of error patterns by category
- Classification Categories — detailed category definitions with sub-patterns, signals, fixes, and risk notes
Repro Command Behavior
By default this skill uses dbt compile to reproduce and validate errors. The command can be customized:
- If the user specifies a different command (e.g.
dbt build,dbt test --select tag:my_tag), use that instead - If a
repro_command.txtfile exists in the project root, use the command from that file
Step 0: Validate Credentials with dbt debug
Before doing anything else, ask the user if they'd like to verify their credentials work on Fusion.
Ask: "Would you like to start by running dbt debug to verify your credentials and connection work on Fusion? This catches environment issues early before we dig into migration errors."
If the user agrees:
Run:
dbt debug
What to check in the output:
- Connection test: Does it say "Connection test: OK"? If not, credentials need fixing first — this is NOT a migration issue
- profiles.yml found: Is it loading the correct profile/target?
- Dependencies: Are packages installed?
If dbt debug fails:
- Connection/auth errors: Help the user fix their
profiles.ymland credentials before proceeding. Migration triage can't begin until the connection works. - Profile not found: Help locate or configure the correct profile for Fusion
- Other errors: Note them and proceed — some
dbt debugchecks may not be relevant to the migration
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.
- 9d ago First seen · 253 lines · 59 tokens per session scan A 5794eec32218
migrating-dbt-core-to-fusion is a skill published in the GitHub repository Kilo-Org/kilo-marketplace (175 stars, last pushed 22d ago), licensed Apache-2.0. It adds 59 tokens to every session and 2,898 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to migrating-dbt-core-to-fusion, differing in 26 lines, and is treated as a copy.
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.