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 configuring-datavault4dbtgit 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/configuring-datavault4dbt)<a href="https://agentmods.dev/skills/scalefreecom/datavault4dbt-agent-skills/configuring-datavault4dbt"><img src="https://agentmods.dev/badge/skills/scalefreecom/datavault4dbt-agent-skills/configuring-datavault4dbt/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/configuring-datavault4dbt"><img src="https://agentmods.dev/badge/skills/scalefreecom/datavault4dbt-agent-skills/configuring-datavault4dbt.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.00094 | $0.01311 |
| Opus 5 | $0.00047 | $0.00656 |
| Sonnet 5 | $0.00019 | $0.00262 |
| Haiku 4.5 | $0.00009 | $0.00131 |
Grade A, and why
configuring-datavault4dbt 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 10d 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 — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Configuring datavault4dbt
Set up the datavault4dbt package and its global variables before building any Data Vault models. Configuration is the prerequisite to every other datavault4dbt task — get the hashing and naming standardized once, project-wide.
1. Install the package
packages.yml:
packages:
- package: ScalefreeCOM/datavault4dbt
version: [">=1.9.0", "<2.0.0"] # 1.9+ allows passing yaml_metadata directly (recommended)
dbt deps
Check the latest version on dbt Hub. v2.0.0 changes hash standardization (hashkeys become
UPPER-normalized, hashdiffs no longer are, plus adapter-specific changes) — values differ from v1. Pin a major range deliberately, and if you later cross the v1→v2 boundary on an existing vault, use therehashing-datavault4dbt-entitiesskill rather than reloading.
2. Verify source requirements
Every source table feeding the vault must be flat & wide in the target database and expose:
- a load date column (arrival time in the source storage), and
- a record source column (where the data came from) — or a static record source you supply in
staging via a
!-prefixed literal.
3. Copy the global variables into your dbt_project.yml
datavault4dbt is driven by vars: prefixed with datavault4dbt.. Copy the full default block from the
installed package (dbt_packages/datavault4dbt/dbt_project.yml) into your project's vars: and adjust
from there. Copying the whole block — not just the ones you change — keeps every adapter-specific
default (timestamps, datatypes) explicit and pinned.
The full default block and what each variable does is in references/global-variables.md. The ones you most often change:
| Variable | Default | Change when |
|---|---|---|
datavault4dbt.hash |
MD5 |
Production: prefer SHA1/SHA2 for collision-resistance |
datavault4dbt.hash_datatype |
STRING |
Must fit the algorithm output and your warehouse |
datavault4dbt.hashkey_input_case_sensitive |
FALSE |
Business keys are case-sensitive in your domain |
datavault4dbt.hashdiff_input_case_sensitive |
TRUE |
Rarely; controls descriptor change detection |
datavault4dbt.ldts_alias / rsrc_alias |
ldts / rsrc |
Your house naming standard differs |
What ships with it
1 file 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.
- 10d ago First seen · 102 lines · 94 tokens per session scan A 2f7825a09ca9
configuring-datavault4dbt is a skill published in the GitHub repository ScalefreeCOM/datavault4dbt-agent-skills (22 stars, last pushed 13d ago), licensed Apache-2.0. It adds 94 tokens to every session and 1,311 once invoked, about $0.0005 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-30.
Other skills, from other repositories
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.
exasol-database
Exasol database interaction via the exapump CLI and Exasol SQL. Covers SQL queries and DML/DDL such as SELECT, INSERT, UPDATE, DELETE, MERGE, CREATE TABLE, ALTER TABLE, and DROP TABLE, CREATE CONNECTION connection objects without import or export intent, schema inspection, table design, exapump sql and exapump…
exasol
Top-level router for Exasol work. Use for any Exasol database, exapump, SQL, BucketFS, extension, integration, UDF, Script Language Container, or Exasol Personal setup task, then route to the narrowest specialized Exasol skill.
exasol-bucketfs
Exasol BucketFS file system management via the exapump bucketfs CLI. Covers listing, uploading, downloading, and deleting files and directories in BucketFS, the bfsdefault service and other bucket services, bucket structure, bfs profile settings, the /buckets/ / / UDF path, and staging JARs, models, and Script…
exasol-distributed-ml
Distributed machine learning, data mining, and iterative HPC with Exasol. Covers end-to-end ML pipelines (DISTRIBUTE BY + SET scripts + BucketFS), per-entity federated training with partialfit and ctx.reset(), batch inference, map-reduce ensemble training, distributed ensemble and SON algorithm for frequent itemset…