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/ingress-configs)<a href="https://agentmods.dev/rules/sfc-gh-cconner/support-rules-mcp/ingress-configs"><img src="https://agentmods.dev/badge/rules/sfc-gh-cconner/support-rules-mcp/ingress-configs/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/sfc-gh-cconner/support-rules-mcp/ingress-configs"><img src="https://agentmods.dev/badge/rules/sfc-gh-cconner/support-rules-mcp/ingress-configs.svg" alt="Reviewed on agentmods" width="80" 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.00741 | $0.00741 |
| Opus 5 | $0.00370 | $0.00370 |
| Sonnet 5 | $0.00148 | $0.00148 |
| Haiku 4.5 | $0.00074 | $0.00074 |
Grade A, and why
ingress-configs 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 8d 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 — 117 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SPCS Ingress Configurations Investigation Guide
PURPOSE: SPCS ingress configurations, Envoy routing, and service endpoint mapping patterns.
Access Method: GitHub MCP API tools
Repository: snowflakedb/snowservices-ingress-configs
🔍 Quick Investigation Patterns
Envoy Configuration
# Envoy routing configs
mcp_github_search_code(
query='route OR cluster OR listener repo:snowflakedb/snowservices-ingress-configs'
)
# Service endpoints
mcp_github_search_code(
query='endpoint OR upstream repo:snowflakedb/snowservices-ingress-configs'
)
# Load balancing
mcp_github_search_code(
query='lb_policy OR load_balancer repo:snowflakedb/snowservices-ingress-configs'
)
Service Mapping
# Service definitions
mcp_github_search_code(
query='service_name OR service_endpoint repo:snowflakedb/snowservices-ingress-configs'
)
# Path routing
mcp_github_search_code(
query='path_match OR prefix repo:snowflakedb/snowservices-ingress-configs'
)
# Header manipulation
mcp_github_search_code(
query='headers OR request_headers_to_add repo:snowflakedb/snowservices-ingress-configs'
)
TLS Configuration
# Certificate management
mcp_github_search_code(
query='tls OR certificate OR ssl repo:snowflakedb/snowservices-ingress-configs'
)
# SNI configuration
mcp_github_search_code(
query='sni OR server_name repo:snowflakedb/snowservices-ingress-configs'
)
🎯 Key Components
Configuration Structure
# Main config files
mcp_github_search_code(
query='config.yaml OR ingress.yaml repo:snowflakedb/snowservices-ingress-configs'
)
# Environment-specific configs
mcp_github_search_code(
query='path:environments repo:snowflakedb/snowservices-ingress-configs'
)
Rate Limiting
# Rate limit configs
mcp_github_search_code(
query='rate_limit OR quota repo:snowflakedb/snowservices-ingress-configs'
)
# Circuit breakers
mcp_github_search_code(
query='circuit_breaker OR outlier_detection repo:snowflakedb/snowservices-ingress-configs'
)
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.
- 8d ago First seen · 117 lines · 741 tokens per session scan A 8a2a53547530
ingress-configs 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 741 tokens to every session, about $0.0037 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.