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 yeaight7/agent-powerups --skill dbt-preflightgit clone --depth 1 https://github.com/yeaight7/agent-powerupsWrote 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/yeaight7/agent-powerups/dbt-preflight)<a href="https://agentmods.dev/skills/yeaight7/agent-powerups/dbt-preflight"><img src="https://agentmods.dev/badge/skills/yeaight7/agent-powerups/dbt-preflight/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/yeaight7/agent-powerups/dbt-preflight"><img src="https://agentmods.dev/badge/skills/yeaight7/agent-powerups/dbt-preflight.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.00046 | $0.00713 |
| Opus 5.5 | $0.00018 | $0.00285 |
| Sonnet 5.5 | $0.00009 | $0.00143 |
| Haiku 4.5 | $0.00005 | $0.00071 |
Grade A, and why
dbt-preflight 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.
How it starts
The opening of the file, as written. The whole thing — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Purpose
Inspect a dbt change set before it ships: identify which assets changed, estimate downstream impact, detect likely gaps in testing, contracts, documentation, and YAML alignment, and recommend the narrowest safe validation path. Preflight is read-only — do not edit code unless explicitly asked.
When to Use
- Before opening a PR in an analytics repository
- Reviewing someone else's dbt change
- Assessing the risk of a change whose downstream impact is unclear
Inputs
- The change set (branch diff or working tree)
- The dbt project, for lineage and selector queries
Workflow
-
Enumerate changed assets:
git diff --name-status origin/main...HEADClassify each change: models, snapshots, seeds, macros, tests, schema YAML, semantic models, metrics, saved queries, exposures or BI-facing assets.
-
Estimate blast radius. For each changed model, list downstream dependents:
dbt ls --select <model>+If a production manifest is available, cover the whole change set at once:
dbt ls --select state:modified+ --state <path-to-prod-artifacts> -
Run the review checklist. Check for:
- model grain changes
- renamed columns or breaking contract changes
- missing or weakened tests
- YAML not updated after model changes
- metrics or semantic definitions drifting from prior meaning
- high blast radius due to downstream dependencies
- incremental logic changes
- snapshot logic changes
- joins or filters that may alter business meaning
-
Recommend the narrowest meaningful validation path first:
- targeted checks:
dbt build --select <changed_model> - narrow downstream checks:
dbt build --select <changed_model>+1 - broader PR-level validation only if needed:
dbt build --select state:modified+ --state <path>
If exact commands are available in the repo (Makefile, CI config, docs), prefer them. If not, say what should be validated conceptually.
- targeted checks:
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 · 83 lines · 46 tokens per session scan A 33c8b7442f79
dbt-preflight is a skill published in the GitHub repository yeaight7/agent-powerups (6 stars, last pushed 19d ago), licensed Apache-2.0. It adds 46 tokens to every session and 713 once invoked, about $0.0002 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-09-14.
Other skills, from other repositories
github-code-review
Review PRs: diffs, inline comments via gh or REST.
requesting-code-review
Pre-commit review: security scan, quality gates, auto-fix.
simplify-code
Sequential 3-lens cleanup of recent code changes.
kodama-constraints
Enforce non-negotiable safety, scope, security, and quality constraints for implementation and review work.
hqe
Comprehensive codebase health auditing, remediation, and verification skill based on the canonical HQE Protocol v5.0.0.
adk-review
Reviews the uncommitted changes in an adk-python working tree and reports correctness, design, public-API stability, test, sample and documentation gaps as a prioritized findings report, fixing them only when asked. Use when the user asks to review local changes, wants a self-review before opening a pull request, asks…