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 agentmods add skills/nevaberry/nevaberry-plugins/dbt-knowledge-patchnpx skills add Nevaberry/nevaberry-plugins --skill dbt-knowledge-patchgit clone --depth 1 https://github.com/Nevaberry/nevaberry-pluginsWrote 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/nevaberry/nevaberry-plugins/dbt-knowledge-patch)<a href="https://agentmods.dev/skills/nevaberry/nevaberry-plugins/dbt-knowledge-patch"><img src="https://agentmods.dev/badge/skills/nevaberry/nevaberry-plugins/dbt-knowledge-patch.svg" alt="Measured on agentmods" 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 | $0.00010 | $0.01961 |
| Opus 5 | $0.00005 | $0.00981 |
| Sonnet 5 | $0.00002 | $0.00392 |
| Haiku 4.5 | $0.00001 | $0.00196 |
Grade A, and why
dbt-knowledge-patch 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 4d 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 — 209 lines — stays where its author put it; the contents beside it link to each section on GitHub.
dbt Core Knowledge Patch
Use this skill when maintaining dbt projects, packages, macros, automation, or adapter integrations that rely on current Core behavior. Start with the quick references below, then open the topic file that matches the task.
Reference Index
| Reference | Topics |
|---|---|
| Behavior Flags and Migrations | Default changes, validation, deprecations, snapshot migration, compatibility flags |
| CLI, Artifacts, and Runtime | Commands, output, parser integration, artifacts, telemetry, dependency floors |
| Incremental Models, Snapshots, and Freshness | Microbatch execution, retries, hard deletes, source and model freshness |
| Managed Functions | SQL, Python, and JavaScript UDF resources, overloads, selection, deferral |
| Project Configuration and Semantic Layer | YAML, metadata, catalogs, Semantic Layer V2, OSI, packages, analyses |
| Testing, Selection, and State | Unit/data tests, selectors, state comparison, resource selection |
Migration Priorities
Audit behavior flags before an upgrade. Keep compatibility opt-outs in the
version-controlled flags block of dbt_project.yml, and remove them after
the project adopts the new behavior.
flags:
require_resource_names_without_spaces: true
source_freshness_run_project_hooks: true
require_generic_test_arguments_property: true
validate_macro_args: true
require_all_warnings_handled_by_warn_error: true
Important default transitions:
require_resource_names_without_spacesandsource_freshness_run_project_hooksdefault totruein Core 1.10. Their legacy opt-outs warn and disappear in Core 2.0.require_generic_test_arguments_propertyarrives disabled in 1.10.5 and defaults totruein 1.10.8. Put generic-test inputs underarguments.validate_macro_argsandrequire_all_warnings_handled_by_warn_errorarrive disabled in 1.10 and default totruein 1.12.- JSON Schema deprecation warnings are on by default in 1.12. Correct invalid project and resource YAML instead of depending on permissive parsing.
What ships with it
7 files 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.
- coverage.json 1.0 KB
- references/behavior-flags-and-migrations.md 5.2 KB
- references/cli-artifacts-and-runtime.md 4.7 KB
- references/incremental-snapshots-and-freshness.md 3.8 KB
- references/managed-functions.md 4.3 KB
- references/project-config-and-semantic-layer.md 4.2 KB
- references/testing-selection-and-state.md 3.3 KB
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.
- 4d ago First seen · 209 lines · 10 tokens per session scan A dd97695abcfe
dbt-knowledge-patch is a skill published in the GitHub repository Nevaberry/nevaberry-plugins (24 stars, last pushed 7d ago), licensed MIT. It adds 10 tokens to every session and 1,961 once invoked, about $0.0001 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
api-context
Canonical reference for the unified Context object passed to every tool and resource handler in @cyanheads/mcp-ts-core. Covers the full interface, its RequestContext base, all sub-APIs (ctx.log, ctx.state, ctx.requestInput, ctx.inputs, ctx.enrich, ctx.content), and when to use each.
api-canvas
DataCanvas primitive reference — a Tier 3 SQL/analytical workspace for tabular MCP servers, backed by DuckDB. Use when registering tables from upstream APIs, running ad-hoc SQL across them, and exporting results. Covers the acquire → register → query → export flow, per-table TTL, the token-sharing pattern for…
api-testing
Testing patterns for MCP tool/resource handlers using createMockContext and Vitest. Covers mock context options, handler testing, McpError assertions, format testing, Vitest config setup, and test isolation conventions.
api-telemetry
Catalog of OpenTelemetry instrumentation built into framework @cyanheads/mcp-ts-core — spans, metrics, completion logs, env config, runtime caveats, custom instrumentation patterns, and cardinality rules. Use when enabling OTel export, adding custom spans or metrics in services, debugging missing telemetry, looking up…
add-test
Scaffold a test file for an existing tool, resource, or service. Use when the user asks to add tests, improve coverage, or when a definition exists without a matching test file.
api-workers
Cloudflare Workers deployment using createWorkerHandler from @cyanheads/mcp-ts-core/worker. Covers the full handler signature, binding types, CloudflareBindings extensibility, runtime compatibility guards, and wrangler.toml requirements.