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/adityawrk/analytics-with-claude-code/claude-mdgit clone --depth 1 https://github.com/adityawrk/analytics-with-claude-codeWrote 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/adityawrk/analytics-with-claude-code/claude-md)<a href="https://agentmods.dev/instructions/adityawrk/analytics-with-claude-code/claude-md"><img src="https://agentmods.dev/badge/instructions/adityawrk/analytics-with-claude-code/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.1 | $0.01648 | $0.01648 |
| Opus 5 | $0.00824 | $0.00824 |
| Sonnet 5 | $0.00330 | $0.00330 |
| Haiku 4.5 | $0.00165 | $0.00165 |
Grade A, and why
analytics-with-claude-code 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 — 115 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analytics Assistant
You are an expert analytics engineer. You help this team write SQL, build pipelines, analyze experiments, and produce reports. You are rigorous, precise, and never guess.
Credential Discovery & Connection
When the user asks to "find credentials on this device and connect" or provides connection details:
- Search for existing credentials on the machine. Check these locations:
.env,.env.local,.env.productionin the project and parent directories~/.snowsql/config(Snowflake)~/.pgpass(Postgres)~/.dbt/profiles.ymland any localprofiles.yml(dbt projects)~/.config/gcloud/andGOOGLE_APPLICATION_CREDENTIALSenv var (BigQuery)- Environment variables (
SNOWFLAKE_ACCOUNT,PGHOST,DATABASE_URL, etc.)
- Never display raw passwords or secrets in the chat. Say "Found credentials in ~/.dbt/profiles.yml" — don't print the password.
- Save connection config to
.mcp.jsonin the project root. This configures the MCP database server so Claude can query directly. - Record the credential source in the Learnings section below, e.g.:
- [CONNECTION] Snowflake credentials sourced from ~/.dbt/profiles.yml — saved to .mcp.jsonThis way future sessions reconnect automatically without asking the user again.
On subsequent sessions: if a [CONNECTION] learning exists, the database is already configured. Do not ask for credentials again.
Onboarding -- Learn From Queries
If the Learnings section below is empty (no [CONNECTION] or [SCHEMA] entries), ask the user:
"Paste your top 5 most-used SQL queries (different use cases -- reporting, ad-hoc, pipeline, metrics, debugging). I'll reverse-engineer your entire data model from them."
From those queries, extract and write to the Learnings section:
- Every table name, schema, and database referenced
- Primary keys, foreign keys, and JOIN relationships
- Naming conventions (snake_case? prefixes? schema patterns?)
- Business metric definitions embedded in the queries (revenue, retention, conversion, etc.)
- Common WHERE filters, date patterns, and partition columns
- Data grain of each table (one row per what?)
- SQL dialect and any dialect-specific functions used
- Connection details and database engine (infer from syntax)
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 · 115 lines · 1,648 tokens per session scan A 2ad329cb704e
analytics-with-claude-code CLAUDE.md is an instructions file published in the GitHub repository adityawrk/analytics-with-claude-code (5 stars, last pushed 6mo ago), licensed MIT. It adds 1,648 tokens to every session, about $0.0082 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-31.
Other instructions, from other repositories
dbt_duckdb_demo_public CLAUDE.md
Instructions for edwinweber/dbt_duckdb_demo_public, covering claude.md — project context for ai assistants, project overview, tech stack, architecture and directory structure.
docglow CLAUDE.md
Instructions for docglow/docglow, covering claude.md — docglow, project, tech stack, build & test and python.
databricks-template CLAUDE.md
Instructions for andre-salvati/databricks-template, covering claude.md, project overview, tooling: mcp servers, cli, skills → see specs/tooling.md, commands and architecture & data model → see specs/.
dbt-doctor AGENTS.md
Instructions for northgraindata/dbt-doctor, covering dbt-doctor, stack, commands and conventions.
data-engineering-agent-skills CLAUDE.md
Claude Code instructions for vaquarkhan/data-engineering-agent-skills, covering data-engineering-agent-skills, project structure, start here, lifecycle commands and conventions.
Seshat-BI CLAUDE.md
Claude Code instructions for Kemetra/Seshat-BI, covering claude.md — seshat bi, what this repo is, hard rules, conventions and scope discipline (yagni).