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/image-registry)<a href="https://agentmods.dev/rules/sfc-gh-cconner/support-rules-mcp/image-registry"><img src="https://agentmods.dev/badge/rules/sfc-gh-cconner/support-rules-mcp/image-registry.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.01656 | $0.01656 |
| Opus 5 | $0.00828 | $0.00828 |
| Sonnet 5 | $0.00331 | $0.00331 |
| Haiku 4.5 | $0.00166 | $0.00166 |
Grade A, and why
image-registry 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 6d 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 — 277 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Snowflake Image Registry Investigation Guide
PURPOSE: Image registry patterns for SPCS container image storage and distribution.
Access Method: GitHub MCP API tools
Repository: snowflakedb/snowflake-image-registry
🔍 Quick Investigation Patterns
Ingress Issues
# Envoy configuration
mcp_github_search_code(
query='path:Envoy/configs repo:snowflakedb/snowflake-image-registry'
)
# Ingress config files
mcp_github_get_file_contents(
owner="snowflakedb", repo="snowflake-image-registry",
path="Envoy/configs/ingress-config.yaml"
)
# Registry config
mcp_github_get_file_contents(
owner="snowflakedb", repo="snowflake-image-registry",
path="Envoy/configs/registry-config.yaml"
)
# WAF/Coraza setup
mcp_github_search_code(
query='coraza OR waf repo:snowflakedb/snowflake-image-registry'
)
Registry Service
# Distribution service
mcp_github_search_code(
query='path:distribution repo:snowflakedb/snowflake-image-registry'
)
# Main registry service
mcp_github_get_file_contents(
owner="snowflakedb", repo="snowflake-image-registry",
path="distribution/main.go"
)
# Snowflake-specific modules
mcp_github_search_code(
query='path:distribution/snowflake repo:snowflakedb/snowflake-image-registry'
)
Authentication & Authorization
# Auth middleware
mcp_github_search_code(
query='path:distribution/snowflake/*/middleware repo:snowflakedb/snowflake-image-registry'
)
# Token handling
mcp_github_search_code(
query='token OR jwt OR auth repo:snowflakedb/snowflake-image-registry'
)
# Registry client auth
mcp_github_search_code(
query='path:registry/client repo:snowflakedb/snowflake-image-registry'
)
Image Operations
# Image copy operations
mcp_github_search_code(
query='path:distribution/snowflake/copy repo:snowflakedb/snowflake-image-registry'
)
# Encryption handling
mcp_github_search_code(
query='path:encryption OR encrypt repo:snowflakedb/snowflake-image-registry'
)
# Manifest handling
mcp_github_search_code(
query='manifest OR blob repo:snowflakedb/snowflake-image-registry'
)
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.
- 6d ago First seen · 277 lines · 1,656 tokens per session scan A c06ea93bb44a
image-registry 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 1,656 tokens to every session, about $0.0083 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
python-containerization-cursorrules-prompt-file
Cursor rules for Python development with containerization integration.
aws-ecs
Definitive guidelines for building, deploying, and operating applications on AWS ECS, emphasizing immutable containers, secure secrets management, and robust operational patterns.
general
Cursor rule "general" from Screenly/Anthias, covering general, project structure, code generation and docker.
hack
Hack v3 is local-first. This project uses hack for local runtime orchestration (compose + DNS/TLS + logs + sessions). Prefer hack when shell access is available. Use MCP only when shell access is unavailable.
colima-docker-runtime
This workspace uses Colima for Docker; use compose-backed tests when Colima is running.
local-compose-db-lifecycle-for-web-tests
Keep local compose DB lifecycle ready for web tests.