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/entropy-data/dataproduct-builder-dbt/copilot-instructionsgit clone --depth 1 https://github.com/entropy-data/dataproduct-builder-dbtWhat 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.01005 | $0.01005 |
| Opus 5 | $0.00502 | $0.00502 |
| Sonnet 5 | $0.00201 | $0.00201 |
| Haiku 4.5 | $0.00101 | $0.00101 |
Grade A, and why
dataproduct-builder-dbt copilot-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 2d 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 — 41 lines — stays where its author put it; the contents beside it link to each section on GitHub.
dataproduct-builder-dbt — Copilot CLI instructions
This file is the plugin's authoritative routing manifest, not a template. It ships at the plugin's repo root and is loaded automatically when you install the plugin with
/plugin install github.com/entropy-data/dataproduct-builder-dbt. Don't copy it into your project — when the plugin updates, this file updates with it.
This repository is a coding-agent plugin that helps build dbt data products and integrate them with Entropy Data. It exposes its capabilities as skills — markdown files under skills/<name>/SKILL.md that you read top-to-bottom and execute step by step.
When a user request matches a skill's trigger, read the corresponding SKILL.md start to finish before acting. Each skill contains audit steps, parameter-gathering, and explicit user-confirmation gates that must not be skipped.
Skills
| When the user asks about… | Follow this skill |
|---|---|
| Scaffolding a brand-new dbt data product from scratch (greenfield, empty directory) | skills/dataproduct-bootstrap/SKILL.md |
| Auditing an existing dbt project against the Entropy Data layout and adding what's missing (ODPS, ODCS, OpenLineage, GitHub Actions, git connections) | skills/entropy-data-sync/SKILL.md |
| Implementing a data product from a published Entropy Data URL or id — derive dbt output-port models from the ODCS schema | skills/dataproduct-implement/SKILL.md |
Editing a data contract (datacontracts/*.odcs.yaml) and testing whether the change is breaking |
skills/datacontract-edit/SKILL.md |
Testing existing data contracts against the live warehouse (no edits — just run datacontract test) |
skills/datacontract-test/SKILL.md |
| Uploading example / sample rows for a data product to Entropy Data | skills/dataproduct-exampledata/SKILL.md |
Listing teams in Entropy Data (e.g. to pick TEAM_NAME as the data product owner) |
skills/entropy-data-teams/SKILL.md |
The trigger phrasing above is illustrative; each SKILL.md's frontmatter description is authoritative. Skills can also call other skills — e.g. dataproduct-bootstrap hands off to entropy-data-sync. Platform-touching skills verify the entropy-data CLI connection with entropy-data connection test as their Step 0 and abort if it fails; they do not prompt for credentials themselves.
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.
- 2d ago First seen · 41 lines · 1,005 tokens per session scan A 3b3296722fa4
dataproduct-builder-dbt copilot-instructions.md is an instructions file published in the GitHub repository entropy-data/dataproduct-builder-dbt (12 stars, last pushed 3mo ago), licensed MIT. It adds 1,005 tokens to every session, about $0.0050 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
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.
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).
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.
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).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.