What is connect-snowflake?

A connection workflow for querying a live Snowflake data warehouse instead of a local DuckDB practice copy. Snowflake is a hosted system for storing and querying large datasets, while DuckDB is a local database.

Use it when you need production or live warehouse numbers, want to query Snowflake tables, or need to confirm whether a query is using Snowflake or DuckDB.

Analysis can give misleading results if it quietly uses a local snapshot instead of current warehouse data. This helps select the remote source and check that the query reached Snowflake.

connect-snowflake — Skill for Claude Code by ai-analyst-lab/ai-analyst

Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo

git clone --depth 1 https://github.com/ai-analyst-lab/ai-analyst

agentmods

npx agentmods add skills/ai-analyst-lab/ai-analyst/connect-snowflake

Made for: Claude Code.

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/ai-analyst-lab/ai-analyst/connect-snowflake/github.svg)](https://agentmods.dev/skills/ai-analyst-lab/ai-analyst/connect-snowflake)

Your own site

<a href="https://agentmods.dev/skills/ai-analyst-lab/ai-analyst/connect-snowflake"><img src="https://agentmods.dev/badge/skills/ai-analyst-lab/ai-analyst/connect-snowflake/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/ai-analyst-lab/ai-analyst/connect-snowflake"><img src="https://agentmods.dev/badge/skills/ai-analyst-lab/ai-analyst/connect-snowflake.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 90 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,370 The whole file, excluding the scripts and references it only reads on demand.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00090	$0.01370
Opus 5.5	$0.00036	$0.00548
Sonnet 5.5	$0.00018	$0.00274
Haiku 4.5	$0.00009	$0.00137

Measured 1mo ago against content hash 1766a0f49664, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

connect-snowflake 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 1mo 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.

.claude/skills/connect-snowflake/SKILL.md · 113 lines

How it starts

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

Skill: Connect to Live Snowflake

Purpose

Run queries against the live Snowflake warehouse — not the local DuckDB practice copy. This is the runbook for "actually go remote." Credentials and config already exist; this skill is about opting into remote and verifying you landed there.

This is distinct from /setup-snowflake (the first-time wizard that collects the connection fields, stores the approved credential in .env, and verifies the native ConnectionManager session). Use this skill when the warehouse is already configured and you just want to query the live data through ConnectionManager.

When to Use

Trigger on any request to use the live/remote Snowflake data, e.g.:

"connect to snowflake", "query snowflake", "use the live data / live warehouse"
"run this against snowflake / the real data / production", "go remote"
"is this hitting snowflake or duckdb?", "query the live tables"
Any analysis where the user explicitly wants live warehouse numbers rather than the local DuckDB practice snapshot

How the repo decides local vs. remote

detect_active_source() (in helpers/data/data_helpers.py) defaults to the local DuckDB copy even though the active dataset declares connection_type: snowflake. It only goes remote when you opt in, via either:

Env flag (per-shell): AAP_USE_REMOTE=1 (also accepts true / yes), OR
Persisted flag: use_remote: true in .knowledge/active.yaml

Set use_remote: true in .knowledge/active.yaml for a persistent opt-in, and set AAP_USE_REMOTE=1 in the same shell command as python3 as a belt-and-suspenders guard. To confirm you actually landed on the warehouse (not the local fallback), call ConnectionManager.verify_remote(): it returns {"remote": bool, "identity": {account, warehouse, database, schema, version}, "reason": ...} from Snowflake's own session context functions. Treat remote: False as "you are NOT on Snowflake" and fix the reason before querying.

Instructions

Read the full file on GitHub · 113 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.

1mo ago Changed · +6 lines 1766a0f49664
1mo ago Changed · +1 lines 3f80b05c3a1e
1mo ago First seen · 106 lines · 90 tokens per session scan A 18ed7694caf9

Subscribe to this mod's changes

connect-snowflake is a skill published in the GitHub repository ai-analyst-lab/ai-analyst (322 stars, last pushed 1mo ago), licensed MIT. It adds 90 tokens to every session and 1,370 once invoked, about $0.0004 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-09-12.

Cloud Databases DevOps and cloud

connect-snowflake next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
connect-snowflakeai-analyst-lab/ai-analyst	Skill	322	1mo ago	MIT	A	90	Claude Code
cloud-databases-onboardinggoogle/skills	Skill	22k	yesterday	Apache-2.0	A	83	Claude Code, Codex
atlas-lakebaseariga/atlas	Skill	8.8k	yesterday	Apache-2.0	A	140	Claude Code
azure-mgmt-mongodbatlas-dotnetmicrosoft/skills	Skill	3.2k	yesterday	MIT	A	64	Claude Code
azure-resource-manager-mysql-dotnetmicrosoft/skills	Skill	3.2k	yesterday	MIT	A	87	Claude Code
azure-resource-manager-redis-dotnetmicrosoft/skills	Skill	3.2k	yesterday	MIT	A	114	Claude Code
azure-resource-manager-sql-dotnetmicrosoft/skills	Skill	3.2k	yesterday	MIT	A	109	Claude Code