dbt-core-mcp: Instructions file for GitHub Copilot

.github/instructions/testing-standards.instructions.md

dbt-core-mcp testing-standards.instructions.md is an instructions file for GitHub Copilot from NiclasOlofsson/dbt-core-mcp. It costs 3,080 tokens per session, scanned A, original, MIT.

Testing rules for tools in dbt-core-mcp, using fast tool-specific tests and shared tests for parsing dbt output. dbt is a tool for transforming data in a warehouse, and MCP is a way for agents to use connected tools.

In plain words
What is it for?
Use them to organize tests for individual tools and shared output parsing, covering successful, failed, empty, skipped, and mixed results.
Why use it?
They make command construction, validation, parsing, errors, and edge cases repeatable to check. The speed requirements help keep the test suite practical during development.

Instructions file for GitHub Copilot

Written for GitHub Copilot: a Copilot instructions file.

This is NiclasOlofsson/dbt-core-mcp's own configuration. It tells GitHub Copilot how to work on dbt-core-mcp itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything dbt-core-mcp configures →

Reuse

Borrowing it

Nothing to install: this file belongs to NiclasOlofsson/dbt-core-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/NiclasOlofsson/dbt-core-mcp/main/.github/instructions/testing-standards.instructions.md
Clone the repo
git clone --depth 1 https://github.com/NiclasOlofsson/dbt-core-mcp

Made for: GitHub Copilot.

Wrote 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.

agentmods badge for dbt-core-mcp testing-standards.instructions.md

README.md
[![agentmods](https://agentmods.dev/badge/instructions/niclasolofsson/dbt-core-mcp/testing-standards.svg)](https://agentmods.dev/instructions/niclasolofsson/dbt-core-mcp/testing-standards)
Your own site
<a href="https://agentmods.dev/instructions/niclasolofsson/dbt-core-mcp/testing-standards"><img src="https://agentmods.dev/badge/instructions/niclasolofsson/dbt-core-mcp/testing-standards.svg" alt="Measured on agentmods" height="20"></a>
Per session 3,080 This file is loaded in full into every session.
When invoked 3,080 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.03080 $0.03080
Opus 5 $0.01540 $0.01540
Sonnet 5 $0.00616 $0.00616
Haiku 4.5 $0.00308 $0.00308

Measured 7d ago against content hash b0b75b549bf3, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

dbt-core-mcp testing-standards.instructions.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 7d 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.

.github/instructions/testing-standards.instructions.md · 370 lines

How it starts

The opening of the file, as written. The whole thing — 370 lines — stays where its author put it; the contents beside it link to each section on GitHub.

dbt-core-mcp Testing Standards

Testing Architecture (2-Layer Strategy)

Layer 1: Tool-Specific Comprehensive Tests

  • Purpose: Command construction, parameter validation, tool-specific business logic
  • Speed Target: < 10 seconds per tool
  • Pattern: Mock external dependencies, use real fixtures for parsing validation
  • Coverage: All command variations, success/failure scenarios, edge cases
  • File: test_tool_{tool_name}.py

Layer 2: Cross-Tool Output Parsing Tests

  • Purpose: Validate parsing of dbt output structures across different scenarios
  • Speed Target: < 5 seconds total
  • Pattern: Real + synthetic fixtures for comprehensive edge case coverage
  • Coverage: Success, failure, mixed, empty, skipped results across all tools
  • File: test_output_parsing.py (shared validation logic)

Performance Requirements

MANDATORY: All tool test suites must achieve < 10 seconds execution time

Target: Fast, comprehensive testing approach

  • Goal: 3-7 seconds with mock-based + fixture approach

File Organization Standards

Test File Structure

tests/
├── test_tool_{tool_name}.py          # Tool-specific: command + parsing + business logic
├── test_output_parsing.py            # Shared: cross-tool output parsing validation
└── fixtures/
    └── target/
        └── run_results.json          # Real dbt output for parsing tests

Consolidated + Shared Pattern (REQUIRED)

  • Tool-Specific Tests: test_tool_{name}.py with complete tool coverage
  • Shared Output Parsing: test_output_parsing.py for cross-tool validation
  • Sections in Tool Tests: Command Construction → Real Fixture Parsing → Business Logic
  • Shared Tests: Edge cases (failed, mixed, empty, skipped) + structure validation

Type Safety Standards

Required Type Annotations

from typing import Any, Callable, Dict, Optional
from unittest.mock import Mock

def test_function(mock_state: Mock) -> None:
    async def capture_invoke(args: Dict[str, Any], progress_callback: Optional[Callable[..., Any]] = None) -> Mock:
        # Implementation

Read the full file on GitHub · 370 lines

Changes

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.

  1. 7d ago First seen · 370 lines · 3,080 tokens per session scan A b0b75b549bf3

Subscribe to this mod's changes

dbt-core-mcp testing-standards.instructions.md is an instructions file published in the GitHub repository NiclasOlofsson/dbt-core-mcp (15 stars, last pushed 4mo ago), licensed MIT. It adds 3,080 tokens to every session, about $0.0154 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.

Related

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.

openai/codex · 5,182 tokens

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).

microsoft/vscode · 6,785 tokens

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.

vercel/next.js · 7,296 tokens

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.

langchain-ai/langchain · 4,469 tokens

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).

microsoft/vscode · 5,001 tokens

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.

github/spec-kit · 7,104 tokens