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/architecturegit 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/architecture)<a href="https://agentmods.dev/rules/sfc-gh-cconner/support-rules-mcp/architecture"><img src="https://agentmods.dev/badge/rules/sfc-gh-cconner/support-rules-mcp/architecture.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.01847 | $0.01847 |
| Opus 5 | $0.00924 | $0.00924 |
| Sonnet 5 | $0.00369 | $0.00369 |
| Haiku 4.5 | $0.00185 | $0.00185 |
Grade A, and why
architecture 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 — 195 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Snowpark Container Services (SPCS) Architecture
PURPOSE: SPCS architecture overview, component relationships, and system design patterns.
Access Method: GitHub MCP API tools
NEVER use local paths - Always use MCP for source code access
🧭 What SPCS Is
- Container platform on Snowflake running user workloads in managed Kubernetes clusters
- Clusters run in VPC separate from warehouses (ExecPlatform)
- GlobalServices (GS) orchestrates SPCS lifecycle and metadata
- Image registry service provides Snowflake-hosted container image repositories
- Ingress via Envoy → public endpoints mapped to SPCS services
- Egress supported via external access integrations (EAIs)
- Private access within SPCS VPC to GS and cloud endpoints
📚 Related Repositories
Runtime and Control Plane Components
snowctl - Cluster runtime
- Repository:
snowflakedb/snowctl - Purpose: Cluster agents, CNI, egress controllers, policy agents, eBPF data paths
- Search:
mcp_github_search_code(query='path:cni/ OR path:egress/ repo:snowflakedb/snowctl')
k8sc-platform - Cluster add-ons
- Repository:
snowflakedb/k8sc-platform - Purpose: Controllers, ArgoCD overlays, ingress controllers, platform components
- Search:
mcp_github_search_code(query='path:argocd/ OR path:controllers/ repo:snowflakedb/k8sc-platform')
Cluster Provisioning - Cloud-specific
- AWS:
snowflakedb/k8s-pulumi-aws - Azure:
snowflakedb/k8s-pulumi-azure - GCP:
snowflakedb/k8s-pulumi-gcp - Search:
mcp_github_search_code(query='Pulumi OR network repo:snowflakedb/k8s-pulumi-aws')
Image Registry and Supply Chain
snowflake-image-registry - Image registry
- Repository:
snowflakedb/snowflake-image-registry - Purpose: Envoy ingress, registry services, SnowFS, TLS, WAF
- Search:
mcp_github_search_code(query='path:Envoy/ OR path:distribution/ repo:snowflakedb/snowflake-image-registry')
container-images - Image building
- Repository:
snowflakedb/container-images - Purpose: Build system, release orchestration, base images, scanning
- Search:
mcp_github_search_code(query='path:release_configs/ OR Dockerfile repo:snowflakedb/container-images')
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 · 195 lines · 1,847 tokens per session scan A 8854d54232f5
architecture 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 1,847 tokens to every session, about $0.0092 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
aws-ecs
Definitive guidelines for building, deploying, and operating applications on AWS ECS, emphasizing immutable containers, secure secrets management, and robust operational patterns.
beanstalk-deploy
Robust deployment patterns for Elastic Beanstalk with GitHub Actions, Pulumi, and edge case handling.
aws-rds-best-practices
AWS RDS PostgreSQL best practices - database configuration, connection management, authentication, backup, and performance optimization standards.
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.