Borrowing it
Nothing to install: this file belongs to sfc-gh-abannerjee/SnowGram. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/sfc-gh-abannerjee/SnowGram/main/.cursor/spcs-best-practices.mdcgit clone --depth 1 https://github.com/sfc-gh-abannerjee/SnowGramWrote 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-abannerjee/snowgram/spcs-best-practices)<a href="https://agentmods.dev/rules/sfc-gh-abannerjee/snowgram/spcs-best-practices"><img src="https://agentmods.dev/badge/rules/sfc-gh-abannerjee/snowgram/spcs-best-practices.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.00008 | $0.00908 |
| Opus 5 | $0.00004 | $0.00454 |
| Sonnet 5 | $0.00002 | $0.00182 |
| Haiku 4.5 | $0.00001 | $0.00091 |
Grade A, and why
spcs-best-practices 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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SPCS Best Practices for SnowGram
Reference for maintaining 85%+ compliance with Snowflake's SPCS best practices.
Critical Security Practices ✅
Secrets Management:
- Always use Snowflake secrets via
secretKeyRefin spec files - Never hardcode credentials in Dockerfiles or code
- Grant secret usage to service roles only
env:
SNOWFLAKE_PASSWORD:
secretKeyRef: snowgram_credentials # ✅ Correct
RBAC:
- Follow principle of least privilege
- Grant only necessary permissions to service roles
- Use dedicated service accounts (SVC_CURSOR, not human accounts)
Deployment Requirements ✅
Docker Image:
- MUST build with
--platform linux/amd64(SPCS requirement) - Use multi-stage builds to minimize size
- No secrets in image layers
Service Specification:
- Fully qualified image paths:
/<database>/<schema>/<repo>/<image>:<tag> - Specify resource requests and limits
- Configure public endpoints with
public: true
Compute Pool:
- Set appropriate instance family (CPU_X64_M for web apps)
- Configure AUTO_SUSPEND_SECS (300-900 seconds)
- Set MIN_NODES and MAX_NODES for scaling
Production Requirements ⚠️
Before Production Deployment:
- Implement health checks (readinessProbe + livenessProbe)
- Scale to MIN_INSTANCES = 2 for high availability
- Set up automated monitoring and alerting
- Configure structured logging (JSON format)
Health Checks Template:
readinessProbe:
httpGet:
path: /health
port: 80
initialDelaySeconds: 30
periodSeconds: 10
failureThreshold: 3
livenessProbe:
httpGet:
path: /health
port: 80
initialDelaySeconds: 60
periodSeconds: 30
failureThreshold: 3
Monitoring Setup ✅
Required Views:
- Service status monitoring (SYSTEM$GET_SERVICE_STATUS)
- Health check history table
- Alert views for failures
Automated Tasks:
- Health check stored procedures (every 5 minutes)
- Resource usage tracking
- Error rate monitoring
High Availability Configuration
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 · 143 lines · 8 tokens per session scan A 1cdf4b6f44ef
spcs-best-practices is a cursor rule published in the GitHub repository sfc-gh-abannerjee/SnowGram (2 stars, last pushed 2mo ago), licensed MIT. It adds 8 tokens to every session and 908 once invoked, about $0.0000 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.
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.