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 ScalefreeCOM/datavault4dbt-agent-skills --skill testing-a-datavault4dbt-projectgit clone --depth 1 https://github.com/ScalefreeCOM/datavault4dbt-agent-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/scalefreecom/datavault4dbt-agent-skills/testing-a-datavault4dbt-project)<a href="https://agentmods.dev/skills/scalefreecom/datavault4dbt-agent-skills/testing-a-datavault4dbt-project"><img src="https://agentmods.dev/badge/skills/scalefreecom/datavault4dbt-agent-skills/testing-a-datavault4dbt-project/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/scalefreecom/datavault4dbt-agent-skills/testing-a-datavault4dbt-project"><img src="https://agentmods.dev/badge/skills/scalefreecom/datavault4dbt-agent-skills/testing-a-datavault4dbt-project.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00081 | $0.01257 |
| Opus 5.5 | $0.00032 | $0.00503 |
| Sonnet 5.5 | $0.00016 | $0.00251 |
| Haiku 4.5 | $0.00008 | $0.00126 |
Grade A, and why
testing-a-datavault4dbt-project 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.
How it starts
The opening of the file, as written. The whole thing — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Testing a datavault4dbt project
Turn the Primary-Key and Foreign-Key assumptions of Data Vault 2 into dbt tests. In DV2 these are soft constraints — implemented as dbt tests that warn (and let you investigate) rather than hard database constraints that would silently drop "bad and ugly" raw data you still want to capture.
Default to soft constraints (dbt tests). Only use hard database constraints if you accept the risk of losing non-conforming raw data and have an Error Mart to catch it.
Where these tests live
Add data_tests in the model's YAML file (colocated with the .sql). Generic tests unique and
not_null are built in; relationships covers FK integrity. For multi-column uniqueness (satellites)
use dbt_utils.unique_combination_of_columns (add the dbt_utils package) or an equivalent.
The technical test matrix
| Entity | Column(s) | Test |
|---|---|---|
| Hub | hashkey | not_null, unique |
| Link | link hashkey | not_null, unique |
| Link | each foreign hashkey | relationships to its connected hub's hashkey |
| Satellite v0 | hashkey + load date | unique combination of columns |
| Satellite v0 | hashkey | relationships to parent hub/link |
| Non-historized link | link hashkey | not_null, unique |
| Non-historized link | each foreign hashkey | relationships to connected hubs |
| Non-historized satellite v0 | hashkey | not_null, unique, relationships to parent NH-link |
| Multi-active satellite v0 | hashkey + load date + multi-active key(s) | unique combination of columns |
| Multi-active satellite v0 | hashkey | relationships to parent hub/link |
| Record-tracking satellite | hashkey + load date | unique combination of columns |
| Record-tracking satellite | hashkey | relationships to parent hub/link |
| Reference hub | reference key(s) | unique, not_null |
| Reference satellite v0 | reference key(s) + load date | unique combination of columns |
(Authoritative source: dbt_packages/datavault4dbt/docs/26_general-usage-notes/40_testing-a-data-vault.)
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 Changed e45690ff46d0
- 17d ago Changed · +6 lines 442389c40a55
- 1mo ago First seen · 112 lines · 81 tokens per session scan A 8f6fcfe34ad4
testing-a-datavault4dbt-project is a skill published in the GitHub repository ScalefreeCOM/datavault4dbt-agent-skills (22 stars, last pushed 7d ago), licensed Apache-2.0. It adds 81 tokens to every session and 1,257 once invoked, about $0.0003 per session on Opus 5.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-30.
Other skills, from other repositories
skill-tester
Runs TDD pressure scenarios against a skill before and after it is written, proving the skill actually changes agent behaviour instead of merely reading well. Use when verifying a new or edited skill has real effect, establishing a RED baseline before authoring, or confirming a GREEN result after.
web-database-validator
Validate database schema, migrations, indexes, and query behavior with structured pass/fail reporting.
grade-iterate
Phase 3 of building a Claude Managed Agent — the bounded grade→iterate loop. Define a CMA outcome (a required markdown rubric graded by an isolated grader), read each verdict, decide the next move (sharpen / re-run / promote to schedule), and once a version passes, run held-back eval cases in parallel. Use when the…
dynamodb
AWS DynamoDB NoSQL database for scalable data storage. Use when designing table schemas, writing queries, configuring indexes, managing capacity, implementing single-table design, or troubleshooting performance issues.
rds
AWS RDS relational database service for managed databases. Use when provisioning databases, configuring backups, managing replicas, troubleshooting connectivity, or optimizing performance.
test-database-seeding
Use when a test needs a database - spin up a dedicated, disposable test database (Testcontainers) seeded with known data, never a shared or production database.