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 rules/sfc-gh-cconner/support-rules-mcp/06-snowflake-cligit clone --depth 1 https://github.com/sfc-gh-cconner/support-rules-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/rules/sfc-gh-cconner/support-rules-mcp/06-snowflake-cli)<a href="https://agentmods.dev/rules/sfc-gh-cconner/support-rules-mcp/06-snowflake-cli"><img src="https://agentmods.dev/badge/rules/sfc-gh-cconner/support-rules-mcp/06-snowflake-cli.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 | $0.02052 | $0.02052 |
| Opus 5 | $0.01026 | $0.01026 |
| Sonnet 5 | $0.00410 | $0.00410 |
| Haiku 4.5 | $0.00205 | $0.00205 |
Grade A, and why
06-snowflake-cli scanned grade A with 1 finding 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 3d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -f https://<service-url>/health How it starts
The opening of the file, as written. The whole thing — 302 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Snowflake CLI Standards
PURPOSE: Snow CLI usage patterns for Snowflake deployments and Snowhouse investigations.
🎯 Core Principles
Quick Checks
snow --version | cat
snow connection test --connection <name> | cat
Non-interactive and Pagerless Execution
- Always pass
--connection <name>explicitly - Avoid interactive prompts; supply all required flags/inputs
- Pipe to
| caton commands that may page output
Consistency First
- Always use Snow CLI for Snowflake resource deployment
- Standardize connection configurations across templates
- Modern practices over legacy approaches
- Environment-driven configurations for flexibility
📋 Configuration Standards
Project File Responsibilities
snowflake.ymldefines resources (apps, services, compute pools, Streamlit); do not put connection credentials here- Manage connections via
snow connection add(preferred) or environment variables
Define a Connection (Once Per Machine/Profile)
snow connection add \
--name default \
--account <account> \
--user <username> \
--authenticator externalbrowser \
--role <role> \
--warehouse <warehouse> \
--database <database> \
--schema <schema> \
--non-interactive | cat
Connection Best Practices
- Use externalbrowser for authentication when possible
- Store connections with
snow connection add; avoid embedding credentials in files - Environment variables for sensitive overrides when needed
- Role-based access with minimal required privileges
- Dedicated warehouses for testing when needed
🔍 Snowhouse Investigation
CRITICAL: Standard Snowhouse Query Pattern
ALWAYS use these parameters when querying Snowhouse:
snow sql --query "<query>" --format=JSON --connection snowhouse
Required Parameters:
--format=JSON- MANDATORY: Provides readable, structured output--connection snowhouse- MANDATORY: Connects to Snowhouse environment
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.
- 3d ago First seen · 302 lines · 2,052 tokens per session scan A c3ca36555335
06-snowflake-cli is a cursor rule published in the GitHub repository sfc-gh-cconner/support-rules-mcp (0 stars, last pushed 10mo ago), licensed Apache-2.0. It adds 2,052 tokens to every session, about $0.0103 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other cursor rules, from other repositories
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
as-contract-cast-smell
// ❌ WRONG — bypasses the family ContractSerializer seam const contract = JSON.parse(raw) as Contract; const contract = JSON.parse(raw) as Contract .
no-backward-compatibility
Do not add backward-compatibility shims or migration scaffolding.
aws-rds-best-practices
AWS RDS PostgreSQL best practices - database configuration, connection management, authentication, backup, and performance optimization standards.
database
Database rules — apply when working with database schemas, queries, migrations, or ORM models.
database
Cursor rule "database" from ItamarZand88/awesome-agent-conventions, covering database best practices, prisma setup, prisma models, prisma queries and supabase setup.