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/09-environment-validationgit 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/09-environment-validation)<a href="https://agentmods.dev/rules/sfc-gh-cconner/support-rules-mcp/09-environment-validation"><img src="https://agentmods.dev/badge/rules/sfc-gh-cconner/support-rules-mcp/09-environment-validation.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.02106 | $0.02106 |
| Opus 5 | $0.01053 | $0.01053 |
| Sonnet 5 | $0.00421 | $0.00421 |
| Haiku 4.5 | $0.00211 | $0.00211 |
Grade A, and why
09-environment-validation 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 4d 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 — 317 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Environment Validation
PURPOSE: Ensures environment is properly configured before Snowflake support operations.
⚠️ IMPORTANT: Environment Setup Required
This rules engine requires proper environment configuration before use. The validation checks for:
- Python 3.8+ - Required for all tools and scripts
- Snow CLI - Required for Snowflake interactions
- GitHub MCP - Required for source code access (replaces 50GB+ of local repos)
- Snowhouse Connection - Required for log analysis
🔍 Current Validation Status
BEFORE PROCEEDING: Your environment validation may be outdated or missing.
To check validation status:
python3 utils/validation_state.py check
🚀 Quick Setup
If validation is missing or outdated, run:
# Option 1: Full setup with GitHub token configuration
bash utils/setup_snowflake_environment.sh --github-token <your-token>
# Option 2: Just validate existing setup
bash utils/validate_project_setup.sh
📋 Getting a GitHub Token
- Go to https://github.com/settings/tokens
- Click "Generate new token" → "Generate new token (classic)"
- Set expiration to 90 days
- Select the "repo" scope (all repo permissions)
- Generate and save the token
⏰ Validation Expiry
- Validation expires after 24 hours to ensure environment stays current
- Version changes in validation requirements trigger re-validation
- Force re-validation anytime:
python3 utils/validation_state.py clear
🎯 Why This Matters
- GitHub MCP eliminates need for 50GB+ of local repositories
- Always up-to-date source code access
- 5,000 API calls/hour for investigations
- Consistent environment across all investigations
✅ Required Components
1. Python 3.8+
# Check Python version
python3 --version
# Should output: Python 3.8.x or higher
Why: All tools and scripts require Python 3.8+
2. Snow CLI
# Check Snow CLI installation
snow --version | cat
# Should output version information
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.
- 4d ago First seen · 317 lines · 2,106 tokens per session scan A 0bbbe3ab7daf
09-environment-validation 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,106 tokens to every session, about $0.0105 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
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.
family-instance-domain-actions
Family instance domain action implementation patterns.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
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.