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/ade-bench --skill ade-bench-cross-db-tasksgit clone --depth 1 https://github.com/dbt-labs/ade-benchWrote 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/ade-bench/ade-bench-cross-db-tasks)<a href="https://agentmods.dev/skills/dbt-labs/ade-bench/ade-bench-cross-db-tasks"><img src="https://agentmods.dev/badge/skills/dbt-labs/ade-bench/ade-bench-cross-db-tasks/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/ade-bench/ade-bench-cross-db-tasks"><img src="https://agentmods.dev/badge/skills/dbt-labs/ade-bench/ade-bench-cross-db-tasks.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.00040 | $0.01985 |
| Opus 5 | $0.00020 | $0.00992 |
| Sonnet 5 | $0.00008 | $0.00397 |
| Haiku 4.5 | $0.00004 | $0.00198 |
Grade A, and why
ade-bench-cross-db-tasks 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 12d 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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ADE-Bench Cross-DB Task Authoring
Overview
Tasks in ade-bench can target DuckDB (default) or Snowflake. A task's files go through a deterministic four-stage lifecycle. Patches that ignore this order produce context mismatches or "reversed patch" prompts that block execution.
Container Lifecycle (in order)
1. MIGRATION shared/migrations/<name>/migration.sh + migration.patch
— Converts shared project files from DuckDB to Snowflake syntax
2. SETUP tasks/<id>/setup.sh + tasks/<id>/setup/changes.patch
tasks/<id>/setup/changes.snowflake.patch (optional)
— Creates the puzzle state the agent must solve
3. AGENT (agent works here)
4. SOLUTION tasks/<id>/solution.sh + tasks/<id>/solutions/changes.patch
tasks/<id>/solutions/changes.snowflake.patch (optional)
Critical: Migration runs before setup and solution. Any line migration touches is in its post-migration state when patches run.
Patch File Pattern
Always apply the base patch, then conditionally apply the snowflake delta. This applies to both setup.sh and solution.sh:
patch -p1 < /app/setup/changes.patch # always (use /sage/solutions/ for solution.sh)
if [[ "$*" == *"--db-type=snowflake"* ]]; then
patch -p1 < /app/setup/changes.snowflake.patch # additive delta only
fi
Never use if/else to choose between two alternative patches. The base patch handles DuckDB; the snowflake patch stacks on top for Snowflake.
changes.snowflake.patch is a delta — it only contains changes that differ from the DuckDB result. It never replicates what migration already did.
Migration Guidelines
Migration's job: Convert DuckDB-specific syntax to Snowflake equivalents across all tasks sharing a project.
- Schema names:
schema: main→schema: public - Date functions:
STRPTIME(...)→TO_DATE(TO_TIMESTAMP(...)) - Generator functions, STRFTIME, etc.
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.
- 12d ago First seen · 160 lines · 40 tokens per session scan A 2d9a3420e937
ade-bench-cross-db-tasks is a skill published in the GitHub repository dbt-labs/ade-bench (123 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 40 tokens to every session and 1,985 once invoked, about $0.0002 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
reproduce-bug
Reproduce a reported bug in googleapis/mcp-toolbox and decide whether it is real, delivering an evidence-backed verdict: confirmed, already fixed, misconfiguration, client-side, works as intended, not reproducible, or blocked. Use whenever a maintainer asks you to reproduce, verify, confirm, or investigate a bug…
fix-failing-tests
Diagnose a failing test in the googleapis/mcp-toolbox repo and land a fix by reasoning from the actual error: read the failure, reproduce it, shrink it until the cause is forced into the open, then fix the cause. Use this whenever a test or CI job is red, a build breaks after a change, many packages fail at once, or a…
triage-issues
Triage GitHub issues in the googleapis/mcp-toolbox repo: propose the correct labels (type / priority / product / status), check for duplicates, verify a bug has enough info to act on, and draft a triage comment. Use whenever a maintainer asks you to triage, label, categorize, prioritize, or "look at" an issue (or a…
postgresql-indexing
PostgreSQL indexing best practices for Prowler: index design, partial indexes, partitioned table indexing, EXPLAIN ANALYZE validation, concurrent operations, monitoring, and maintenance. Trigger: When creating or modifying PostgreSQL indexes, analyzing query performance with EXPLAIN, debugging slow queries, reviewing…
graphjin-eval
Create, extend, run, baseline, and diagnose GraphJin agent evaluations through the graphjin eval CLI.
axiom-audit-grdb-performance
Use when the user mentions GRDB performance review, slow GRDB queries, app-group database setup audit, a ValueObservation that stopped updating, or pre-release GRDB scan.