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 adding-dbt-unit-testgit 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/adding-dbt-unit-test)<a href="https://agentmods.dev/skills/kilo-org/kilo-marketplace/adding-dbt-unit-test"><img src="https://agentmods.dev/badge/skills/kilo-org/kilo-marketplace/adding-dbt-unit-test/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/adding-dbt-unit-test"><img src="https://agentmods.dev/badge/skills/kilo-org/kilo-marketplace/adding-dbt-unit-test.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.00044 | $0.03831 |
| Opus 5 | $0.00022 | $0.01916 |
| Sonnet 5 | $0.00009 | $0.00766 |
| Haiku 4.5 | $0.00004 | $0.00383 |
Grade A, and why
adding-dbt-unit-test 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 6d 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
91% identical to adding-dbt-unit-test — 64 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 — 362 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Add unit test for a dbt model
Additional Resources
- Spec Reference - All required and optional YAML keys for unit tests
- Examples - Unit test examples across formats (dict, csv, sql)
- Incremental Models - Unit testing incremental models
- Ephemeral Dependencies - Unit testing models depending on ephemeral models
- Special Case Overrides - Introspective macros, project variables, environment variables
- Versioned Models - Unit testing versioned SQL models
- BigQuery Caveats - BigQuery-specific caveats
- BigQuery Data Types - BigQuery data type handling
- Postgres Data Types - Postgres data type handling
- Redshift Caveats - Redshift-specific caveats
- Redshift Data Types - Redshift data type handling
- Snowflake Data Types - Snowflake data type handling
- Spark Data Types - Spark data type handling
What are unit tests in dbt
dbt unit tests validate SQL modeling logic on static inputs before materializing in production. If any unit test for a model fails, dbt will not materialize that model.
When to use
You should unit test a model:
- Adding Model-Input-Output scenarios for the intended functionality of the model as well as edge cases to prevent regressions if the model logic is changed at a later date.
- Verifying that a bug fix solves a bug report for an existing dbt model.
More examples:
- When your SQL contains complex logic:
- Regex
- Date math
- Window functions
case whenstatements when there are manywhens- Truncation
- Complex joins (multiple joins, self-joins, or joins with non-trivial conditions)
- When you're writing custom logic to process input data, similar to creating a function.
- Logic for which you had bugs reported before.
- Edge cases not yet seen in your actual data that you want to be confident you are handling properly.
- Prior to refactoring the transformation logic (especially if the refactor is significant).
- Models with high "criticality" (public, contracted models or models directly upstream of an exposure).
What ships with it
13 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.
- references/examples.md 4.5 KB
- references/spec.md 1.6 KB
- references/special-cases-ephemeral-dependency.md 432 B
- references/special-cases-incremental-model.md 2.6 KB
- references/special-cases-special-case-overrides.md 1.9 KB
- references/special-cases-versioned-model.md 876 B
- references/warehouse-bigquery-caveats.md 149 B
- references/warehouse-bigquery-data-types.md 1.2 KB
- references/warehouse-postgres-data-types.md 750 B
- references/warehouse-redshift-caveats.md 754 B
- references/warehouse-redshift-data-types.md 694 B
- references/warehouse-snowflake-data-types.md 823 B
- references/warehouse-spark-data-types.md 664 B
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.
- 6d ago First seen · 362 lines · 44 tokens per session scan A db4c0abb2fb3
adding-dbt-unit-test is a skill published in the GitHub repository Kilo-Org/kilo-marketplace (174 stars, last pushed 19d ago), licensed Apache-2.0. It adds 44 tokens to every session and 3,831 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to adding-dbt-unit-test, differing in 64 lines, and is treated as a copy.
Other skills, from other repositories
migrate-xunit-to-xunit-v3
Migrate .NET test projects from xUnit.net v2 to xunit.v3 and fix v3 breaks. Use for package/CPM conversion, OutputType=Exe, preserving the VSTest or MTP runner (including projects currently using YTest.MTP.XUnit2), incompatible TFMs, async void tests, string-to-Type attributes, custom Fact/Theory/BeforeAfterTest…
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
nw-fp-clojure
Clojure language-specific patterns, data-first modeling, REPL-driven development, and spec.
mobiai-ios-testing
Use when writing or running tests in an iOS project — unit tests, UI tests, snapshot tests, choosing the right framework.
restore-internals-seams-in-finally-blocks-after-each-test
When delegating a task affected by this skill, include.
testing-llm
LLM and AI testing patterns — mock responses, evaluation with DeepEval/RAGAS, structured output validation, and agentic test patterns (generator, healer, planner). Use when testing AI features, validating LLM outputs, or building evaluation pipelines.