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.
curl -O https://raw.githubusercontent.com/NiclasOlofsson/dbt-core-mcp/main/.github/instructions/memory.instructions.mdgit clone --depth 1 https://github.com/NiclasOlofsson/dbt-core-mcpWrote 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/niclasolofsson/dbt-core-mcp/memory)<a href="https://agentmods.dev/instructions/niclasolofsson/dbt-core-mcp/memory"><img src="https://agentmods.dev/badge/instructions/niclasolofsson/dbt-core-mcp/memory/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/instructions/niclasolofsson/dbt-core-mcp/memory"><img src="https://agentmods.dev/badge/instructions/niclasolofsson/dbt-core-mcp/memory.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00978 | $0.00978 |
| Opus 5.5 | $0.00391 | $0.00391 |
| Sonnet 5.5 | $0.00196 | $0.00196 |
| Haiku 4.5 | $0.00098 | $0.00098 |
Grade A, and why
dbt-core-mcp memory.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 2mo 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 — 81 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workspace AI Memory
This file contains workspace-specific information for AI conversations.
Universal Laws
-
dbt-core-mcp Pre-Commit Validation Protocol:
- STEP 1: Before staging/committing ANY code changes, run CI validation sequence in order:
- a)
uv run ruff check src tests - b)
uv run ruff format --check src tests - c)
uv run pyright src tests - d)
uv run pytest
- a)
- STEP 2: Verify ALL steps succeed with exit code 0
- STEP 3: If ANY step fails, fix issues and restart from STEP 1
- STEP 4: Restore
.vscode/mcp.jsonto original state (revert_RESTARTcounter changes)- Use
git restore .vscode/mcp.jsonOR manually revert counter - NEVER commit restart counter changes - testing only
- Use
- STEP 5: Only after all checks pass and cleanup complete, proceed with
git add/commit/push - APPLIES TO: All code commits in dbt-core-mcp workspace
- VIOLATION PENALTY: Immediate acknowledgment and restart with correct procedure
- NO EXCEPTIONS
- STEP 1: Before staging/committing ANY code changes, run CI validation sequence in order:
-
Selective Testing Protocol:
- RUN
pytestto validate implementations and verify code works - Tests provide definitive feedback on whether changes are correct
- Use tests during development to catch issues early
- For targeted testing: run specific test files or functions when fixing particular issues
- Pre-commit validation always requires full test suite (Law 1 requirement)
- Let tests decide if implementation works rather than guessing
- For complete validation:
uv run ruff check src tests && uv run ruff format --check src tests && uv run pyright src tests && uv run pytest - NO EXCEPTIONS
- RUN
-
Git Commit Amendment Protocol:
- When fixing issues in the MOST RECENT commit (before anyone else pulls):
- Use
git commit --amend --no-editto fix without creating new commit - Use
git push --forceto rewrite remote history - Keeps git history clean for release notes
- Use
- ONLY amend if commit hasn't been pulled by others
- Examples: formatting fixes, typos, forgot to add files after initial commit
- DO NOT create second commits for fixes to recent work (clutters release notes)
- APPLIES TO: All git operations in dbt-core-mcp workspace
- NO EXCEPTIONS
- When fixing issues in the MOST RECENT commit (before anyone else pulls):
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.
- 2mo ago First seen · 81 lines · 978 tokens per session scan A c2f004478192
dbt-core-mcp memory.instructions.md is an instructions file published in the GitHub repository NiclasOlofsson/dbt-core-mcp (15 stars, last pushed 6mo ago), licensed MIT. It adds 978 tokens to every session, about $0.0039 per session on Opus 5.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
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).
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.