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/netgit 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/net)<a href="https://agentmods.dev/rules/sfc-gh-cconner/support-rules-mcp/net"><img src="https://agentmods.dev/badge/rules/sfc-gh-cconner/support-rules-mcp/net.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.00660 | $0.00660 |
| Opus 5 | $0.00330 | $0.00330 |
| Sonnet 5 | $0.00132 | $0.00132 |
| Haiku 4.5 | $0.00066 | $0.00066 |
Grade A, and why
net 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 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.
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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Snowflake .NET Connector Investigation Guide
PURPOSE: .NET connector patterns for C# and .NET applications connecting to Snowflake.
Access Method: GitHub MCP API tools
Repository: snowflakedb/snowflake-connector-net
🔍 Quick Investigation Patterns
Session & Authentication
# Session management
mcp_github_search_code(
query='SFSession OR SessionPool repo:snowflakedb/snowflake-connector-net'
)
# Authentication
mcp_github_search_code(
query='Authenticator OR Login repo:snowflakedb/snowflake-connector-net'
)
# Key pair auth
mcp_github_search_code(
query='PrivateKey OR JWT repo:snowflakedb/snowflake-connector-net'
)
Command Execution
# Statement execution
mcp_github_search_code(
query='SnowflakeDbCommand OR ExecuteQuery repo:snowflakedb/snowflake-connector-net'
)
# Result handling
mcp_github_search_code(
query='SnowflakeDbDataReader OR ResultSet repo:snowflakedb/snowflake-connector-net'
)
# Async operations
mcp_github_search_code(
query='async OR await OR Task repo:snowflakedb/snowflake-connector-net'
)
File Transfer
# PUT/GET operations
mcp_github_search_code(
query='path:FileTransfer repo:snowflakedb/snowflake-connector-net'
)
# Staging operations
mcp_github_search_code(
query='UploadFile OR DownloadFile repo:snowflakedb/snowflake-connector-net'
)
🎯 Key Components
Core Classes
# Connection class
mcp_github_get_file_contents(
owner="snowflakedb", repo="snowflake-connector-net",
path="Snowflake.Data/Core/SFConnection.cs"
)
# Session implementation
mcp_github_get_file_contents(
owner="snowflakedb", repo="snowflake-connector-net",
path="Snowflake.Data/Core/SFSession.cs"
)
# REST client
mcp_github_get_file_contents(
owner="snowflakedb", repo="snowflake-connector-net",
path="Snowflake.Data/Core/RestRequester.cs"
)
🗺️ Directory Structure
Snowflake.Data/
├── Core/ # Session, login, network
├── Client/ # Commands, statements
├── FileTransfer/ # PUT/GET operations
├── Logger/ # Logging utilities
└── Configuration/ # Client config
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 · 107 lines · 660 tokens per session scan A e04e7c7eb175
net 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 660 tokens to every session, about $0.0033 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
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
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.
postgresql
强制执行 PostgreSQL 编码标准、最佳实践和性能优化技术，以确保可维护、高效和安全的数据库交互。此规则涵盖代码格式、数据完整性、安全性和性能考虑。.
firebase
Best practices for Firebase integration including Authentication, Firestore, Storage, and Functions.