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.
git 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/10-project-overview)<a href="https://agentmods.dev/rules/sfc-gh-cconner/support-rules-mcp/10-project-overview"><img src="https://agentmods.dev/badge/rules/sfc-gh-cconner/support-rules-mcp/10-project-overview.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.02122 | $0.02122 |
| Opus 5 | $0.01061 | $0.01061 |
| Sonnet 5 | $0.00424 | $0.00424 |
| Haiku 4.5 | $0.00212 | $0.00212 |
Grade A, and why
10-project-overview 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 7d 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 — 257 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Overview & Context
PURPOSE: High-level project context, purpose, and structure for Snowflake Support Rules MCP.
📘 Project Purpose
This is an MCP (Model Context Protocol) Server that provides structured rules and guidance for AI assistants working on Snowflake-related support tasks.
Target Users: AI assistants helping IC5-level support engineers with:
- Root Cause Analysis: Finding issues in Snowflake source code
- Customer Issue Troubleshooting: Systematic approach to complex problems
- Reusable Reproductions: Building parameterized, shareable reproduction templates
- Runbook Development: Creating comprehensive troubleshooting procedures
🎯 What This MCP Server Provides
Core Rules Categories
-
Core Rules (
rules/core/):- GitHub MCP integration for source code access
- Snowflake documentation search
- Code quality and examples via Context7
- DPO to Snowhouse table mappings
- Snowhouse querying patterns
- Snow CLI usage for investigations
- Mono repo structure and navigation
- Environment validation requirements
- Project standards (git, docs, testing, security)
-
Connector Rules (
rules/connectors/):- Python connector patterns
- JDBC connector guidance
- Go driver (gosnowflake)
- Node.js connector
- .NET connector
- Snowpark Python
- Kafka connector
- Spark connector
- ML Python
- Ingest Java
- Terraform provider
-
SPCS Rules (
rules/spcs/):- Architecture overview
- Snowctl (cluster runtime agents)
- Image registry
- Container images
- Ingress configurations
- K8SC platform
- K8s Pulumi (AWS, Azure, GCP)
- Artifactory
-
Workflow Rules (
rules/workflows/):- Troubleshooting procedures
- Reproduction creation patterns
- Stored procedure development
- AI collaboration guidelines
- Template standards
- Runbook development
- Naming conventions
- Technical decisions
-
Meta Rules (
rules/_meta/):- Complete workflow orchestration
- Includes multiple rules for end-to-end tasks
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.
- 7d ago First seen · 257 lines · 2,122 tokens per session scan A d252880c8b79
10-project-overview is a cursor rule published in the GitHub repository sfc-gh-cconner/support-rules-mcp (0 stars, last pushed 11mo ago), licensed Apache-2.0. It adds 2,122 tokens to every session, about $0.0106 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 cursor rules, from other repositories
ponytail
Ponytail, lazy senior dev mode. Always pick the simplest solution that works.
angular-20
This rule provides comprehensive best practices and coding standards for Angular development, focusing on modern TypeScript, standalone components, signals, and performance optimizations.
dev-standard
Apache Superset development standards and guidelines for Cursor IDE.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.