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 dbt-labs/dbt-agent-skills --skill maintaining-dbt-documentationgit clone --depth 1 https://github.com/dbt-labs/dbt-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/dbt-labs/dbt-agent-skills/maintaining-dbt-documentation)<a href="https://agentmods.dev/skills/dbt-labs/dbt-agent-skills/maintaining-dbt-documentation"><img src="https://agentmods.dev/badge/skills/dbt-labs/dbt-agent-skills/maintaining-dbt-documentation/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/dbt-labs/dbt-agent-skills/maintaining-dbt-documentation"><img src="https://agentmods.dev/badge/skills/dbt-labs/dbt-agent-skills/maintaining-dbt-documentation.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.00077 | $0.01877 |
| Opus 5 | $0.00039 | $0.00938 |
| Sonnet 5 | $0.00015 | $0.00375 |
| Haiku 4.5 | $0.00008 | $0.00188 |
Grade A, and why
maintaining-dbt-documentation 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 11d 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 — 138 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Maintaining dbt Documentation
Keep a dbt project's model and column documentation complete and consistent as it grows. This skill (1) audits which models lack YAML documentation, (2) drafts the missing descriptions in the conventions the project already uses — working one folder at a time — and (3) leaves every change for the user to review. It never commits or pushes.
Two ways it's used:
- Backfill — document a folder of undocumented models on a project that has drifted below full coverage.
- Keep in sync — after models are added or their SQL changes (common when many contributors are landing models), run the audit to find the gap, document just those, and re-verify.
This is the systematic, coverage-driven companion to using-dbt-for-analytics-engineering
(which covers one-off model building and its references/writing-documentation.md
guide). Use that skill for the content principles of a good description; use this
one to find the gaps and backfill them at scale in a consistent style.
Match the project's conventions — do not impose your own
Before drafting anything, read several already-documented models and mirror what you find. dbt projects vary widely; infer and follow the local house style rather than a generic template. Determine:
- YAML layout — one shared schema file per folder (named after the folder), one
.ymlper model, or a single project-wide file? Add new entries where existing ones live. Only create a new file (version: 2+models:) if the folder has none. - Description mechanism — inline
description:strings, or{% docs %}blocks referenced with{{ doc('...') }}? Follow whichever the project uses. - Description shape — do descriptions lead with grain ("One row per …")? State
the primary key, key foreign keys, and upstream sources? Single-line for simple
staging models vs. folded blocks (
description: >) for models with caveats? Copy the observed pattern. - Column coverage — which columns get documented (all, vs. keys + derived only)? Match the neighbours' depth.
- Test placement — inline
tests:/data_tests:, and on which columns?
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.
- 11d ago First seen · 138 lines · 77 tokens per session scan A 61359d2f9fec
maintaining-dbt-documentation is a skill published in the GitHub repository dbt-labs/dbt-agent-skills (708 stars, last pushed 2d ago), licensed Apache-2.0. It adds 77 tokens to every session and 1,877 once invoked, about $0.0004 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
create-pr
Creates a GitHub PR with a Linear-ticket-prefixed title and a decision-led, narrative description for prisma-next. Use when the user wants to create a pull request, open a PR, or submit changes for review.
schema-exploration
Lists tables, describes columns and data types, identifies foreign key relationships, and maps entity relationships in a database. Use when the user asks about database schema, table structure, column types, what tables exist, ERD, foreign keys, or how entities relate.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
supabase
Supabase / PostgREST Row-Level-Security playbook — pull the anon (or leaked servicerole) key out of the frontend JS, map tables from the auto-generated OpenAPI spec, test anonymous RLS READ disclosures (PII/secret leaks), and anonymous RLS WRITE abuse (insert/update/delete — e.g. forging…
nornicdb-cypher-queries
Pick fast, predictable Cypher query shapes in NornicDB — point lookups, batch retrieval, pagination, search, traversal, batched UNWIND/MERGE writes, cleanup, multi-tenant isolation. Use when writing or reviewing Cypher whose latency or throughput matters; maps user intent to the executor's hot-path query templates.
dsql
Build with Aurora DSQL — manage schemas, execute queries, handle migrations, diagnose query plans, diagnose cluster performance, load data, and develop applications with a serverless, distributed SQL database. Covers IAM auth, multi-tenant patterns, MySQL-to-DSQL and PostgreSQL-to-DSQL schema conversion, foreign key…