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 instructions/dbt-labs/ade-bench/claude-mdgit 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/instructions/dbt-labs/ade-bench/claude-md)<a href="https://agentmods.dev/instructions/dbt-labs/ade-bench/claude-md"><img src="https://agentmods.dev/badge/instructions/dbt-labs/ade-bench/claude-md.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.01359 | $0.01359 |
| Opus 5 | $0.00679 | $0.00679 |
| Sonnet 5 | $0.00272 | $0.00272 |
| Haiku 4.5 | $0.00136 | $0.00136 |
Grade A, and why
ade-bench CLAUDE.md 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 5d 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 — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md - ADE-Bench Development Notes
Project Overview
ADE-Bench (Analytics and Data Engineering Benchmark) is a benchmarking framework for evaluating AI agents on data analyst tasks. It's modeled after terminal-bench but specialized for dbt and SQL workflows.
Key Differences from Terminal-Bench
- Containers: Include dbt + database (DuckDB/SQLite/PostgreSQL) instead of general dev environments
- Tests: SQL queries validate results instead of pytest
- Tasks: Focus on data transformations, aggregations, and analytics
Architecture
Core Components
harness.py: Main orchestrator for running benchmarkstrial_handler.py: Manages individual task executionsql_parser.py: Validates task results using SQL queriesdocker_compose_manager.py: Handles dbt/database containers
Directory Structure
ade-bench/
├── ade_bench/ # Core Python package
├── tasks/ # Individual task definitions
├── docker/base/ # Base Docker images
├── shared/defaults/ # Default configurations
├── experiments/ # Benchmark results
└── datasets/ # Dataset configurations
Task Structure
Each task contains:
task.yaml: Metadata and configurationdbt_project/: dbt project filestests/: SQL validation queriesexpected/: Expected query resultssolution.sh: Reference solutionDockerfile: Container setup (optional, uses defaults)
Running Commands
Create a new task:
uv run wizard
Run benchmarks:
# With sage agent
uv run scripts_python/run_harness.py --agent sage --task-ids task1 task2
Key Parameters:
--agent: Agent type (sage, claude, codex, gemini, etc.)--model: LLM model for AI agents--dataset-config: YAML file defining task collection--n-concurrent-trials: Parallel execution (default: 4)--no-rebuild: Skip Docker rebuilds--cleanup: Remove Docker resources after run--plugin-set: Plugin set names fromexperiment_sets/plugin-sets.yaml(space-separated). Controls skills, MCP servers, and allowed tools. Defaults tonone(no plugins).
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.
- 5d ago First seen · 184 lines · 1,359 tokens per session scan A 50eae97107c9
ade-bench CLAUDE.md is an instructions file published in the GitHub repository dbt-labs/ade-bench (122 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 1,359 tokens to every session, about $0.0068 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 instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).