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/stored-procedures)<a href="https://agentmods.dev/rules/sfc-gh-cconner/support-rules-mcp/stored-procedures"><img src="https://agentmods.dev/badge/rules/sfc-gh-cconner/support-rules-mcp/stored-procedures.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.00533 | $0.00533 |
| Opus 5 | $0.00267 | $0.00267 |
| Sonnet 5 | $0.00107 | $0.00107 |
| Haiku 4.5 | $0.00053 | $0.00053 |
Grade A, and why
stored-procedures 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Stored Procedures Generation - Complete Ruleset
PURPOSE: Complete workflow for developing Snowflake stored procedures with code examples, documentation access, and quality standards.
Meta-Rule: This combines core Snowflake knowledge, code quality guidance, and stored procedure patterns.
📦 Included Rules
This meta-rule includes:
- ✅ Core: Source code access (GitHub MCP)
- ✅ Core: Documentation access (Snowflake Docs MCP)
- ✅ Core: Code quality & examples (Context7 MCP)
- ✅ Core: DPO to table mappings
- ✅ Core: Snowhouse querying patterns
- ✅ Workflow: Stored procedure generation guide
@include core/01-github-mcp.mdc @include core/02-docs-mcp.mdc @include core/03-code-quality-mcp.mdc @include core/04-dpo-mappings.mdc @include core/05-snowhouse-querying.mdc @include workflows/stored-procedures.mdc
🎯 Quick Reference
Procedure Development Flow
- Define Requirements → What data to collect?
- Map DPOs → Which tables to query?
- Get Examples → Context7 for best practices
- Build Query → Snowhouse patterns
- Write Procedure → With error handling
- Test → Validate functionality
- Document → Complete usage guide
Key Principles
- Always validate inputs
- Use type hints
- Add comprehensive error handling
- Include logging
- Write to temp tables for large results
- Document thoroughly
Code Quality Resources
# Get Snowpark examples
mcp_context7_get-library-docs(
context7CompatibleLibraryID="/snowflakedb/snowpark-python",
topic="stored procedures best practices",
tokens=2000
)
# Get error handling patterns
mcp_context7_get-library-docs(
context7CompatibleLibraryID="/snowflakedb/snowpark-python",
topic="exception handling",
tokens=1500
)
Critical Reminders
- Image repos →
stage_etl_vwithstage_type = 'IMAGE_REPOSITORY' - Git repos →
stage_etl_vwithstage_type = 'GIT_REPOSITORY' - Always filter by
account_id - Always use time bounds
- Always include LIMIT for safety
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 · 76 lines · 533 tokens per session scan A 85d453e34f12
stored-procedures 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 533 tokens to every session, about $0.0027 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.
as-contract-cast-smell
// ❌ WRONG — bypasses the family ContractSerializer seam const contract = JSON.parse(raw) as Contract; const contract = JSON.parse(raw) as Contract .
no-backward-compatibility
Do not add backward-compatibility shims or migration scaffolding.
postgresql
This guide defines the definitive best practices for writing clean, performant, and maintainable PostgreSQL SQL, focusing on modern conventions and avoiding common pitfalls.
query-optimization
A database performance rule that requires measuring PostgreSQL queries with EXPLAIN ANALYZE under the same user permissions and row-level security (RLS) conditions used in production.
ehs-ims-conventions
EHS IMS app — RBAC, data layer, tRPC, migrations, AI boundaries.