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 ulises-jeremias/agent-toolkit --skill dbt-validationgit clone --depth 1 https://github.com/ulises-jeremias/agent-toolkitWrote 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/ulises-jeremias/agent-toolkit/dbt-validation)<a href="https://agentmods.dev/skills/ulises-jeremias/agent-toolkit/dbt-validation"><img src="https://agentmods.dev/badge/skills/ulises-jeremias/agent-toolkit/dbt-validation/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/ulises-jeremias/agent-toolkit/dbt-validation"><img src="https://agentmods.dev/badge/skills/ulises-jeremias/agent-toolkit/dbt-validation.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.00037 | $0.00393 |
| Opus 5.5 | $0.00015 | $0.00157 |
| Sonnet 5.5 | $0.00007 | $0.00079 |
| Haiku 4.5 | $0.00004 | $0.00039 |
Grade A, and why
dbt-validation 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 1mo 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.
What it actually says
dbt validation (HOW)
Use when the repository is a dbt project or the task requires dbt verification. Client workflows may delegate here.
Boundaries
- Follow repo
AGENTS.md,Makefile,README, and CI—not generic guesses. - Do not change Snowflake security settings, network rules, or warehouse admin from this skill.
- If
dbtor credentials are missing, say so and do not claim validation passed.
Discovery
Look for dbt_project.yml, packages.yml, models/, Makefile, pyproject.toml, or CI jobs that invoke dbt.
Typical commands (examples only—prefer repo docs)
| Intent | Often used (verify in repo) |
|---|---|
| Syntax / graph | dbt parse, dbt compile |
| Dependencies | dbt deps when packages change |
| Tests | dbt test or subset flags the repo documents |
| Build | dbt run / dbt build when the user approves mutating runs |
Makefile wrappers (e.g. make parse) take precedence when documented.
Evidence
- Summarize which commands ran and high-level outcome (pass/fail/skipped) for tickets and PRs.
- On failure, capture actionable error lines; do not dump full logs unless the user asks.
Safety
- Prefer read-only checks (
parse,compile,test) when the task is review-only. - Production runs require explicit user approval per repo policy.
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.
- 1mo ago First seen · 42 lines · 37 tokens per session scan A 6d180ee3b0fe
dbt-validation is a skill published in the GitHub repository ulises-jeremias/agent-toolkit (19 stars, last pushed 2d ago), licensed MIT. It adds 37 tokens to every session and 393 once invoked, about $0.0001 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
data-quality-frameworks
Implement data quality validation with Great Expectations, dbt tests, and data contracts. Use when building data quality pipelines, implementing validation rules, or establishing data contracts.
AI System Quality Engineer
Test LLM, RAG, MCP, and agentic systems end to end. Build golden datasets, run deterministic checks and LLM judges, score retrieval, probe prompt injection, verify tool use, and gate CI on thresholds. Orchestrates DeepEval, Ragas, promptfoo, and Langfuse.
hotfix
Fixes an observed defect with reproducible evidence in one call: writes a short trace doc before touching code, implements the fix, and backs it with a regression test written before the fix. Production incidents are the motivating case, not a gate. When blocked, it halts by name and saves the doc for a later call to…
test-case-to-katalon-studio
Convert Katalon True Platform/TestOps manual test cases into Katalon Studio automation inside a local Studio Test Project checkout. Use when you need to author or extend a .tc test case file and its paired Groovy script under Scripts/, keep test case variable GUIDs consistent with the .ts test suite bindings that read…
test-estimation
Estimate testing effort, duration, and resourcing for a Katalon True Platform/TestOps cycle. Use when the question is how long testing will take, how many testers it needs, whether the scope fits the sprint window, or what a scope change costs in person-hours. Sizes design, manual execution, automated execution and…
test-reporting
Report Katalon True Platform/TestOps quality metrics to people outside QA. Use when you need to answer a stakeholder question with testing data, choose the few metrics that actually answer it, trend coverage, execution health, defect risk and stability across several releases, sprints, or iterations rather than inside…