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/container-imagesgit 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/container-images)<a href="https://agentmods.dev/rules/sfc-gh-cconner/support-rules-mcp/container-images"><img src="https://agentmods.dev/badge/rules/sfc-gh-cconner/support-rules-mcp/container-images.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.00545 | $0.00545 |
| Opus 5 | $0.00272 | $0.00272 |
| Sonnet 5 | $0.00109 | $0.00109 |
| Haiku 4.5 | $0.00055 | $0.00055 |
Grade A, and why
container-images 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 5d 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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Container Images Build & Release Investigation Guide
PURPOSE: Container image build, release tooling, and base image patterns for SPCS.
Access Method: GitHub MCP API tools
Repository: snowflakedb/container-images
🔍 Quick Investigation Patterns
Image Build System
# Dockerfile definitions
mcp_github_search_code(
query='Dockerfile OR FROM repo:snowflakedb/container-images'
)
# Build configurations
mcp_github_search_code(
query='build.yaml OR release repo:snowflakedb/container-images'
)
# Base images
mcp_github_search_code(
query='path:base-images repo:snowflakedb/container-images'
)
Release Orchestration
# Release configs
mcp_github_search_code(
query='path:release_configs repo:snowflakedb/container-images'
)
# Version management
mcp_github_search_code(
query='version OR tag OR release repo:snowflakedb/container-images'
)
# CI/CD pipelines
mcp_github_search_code(
query='pipeline OR jenkins OR github-actions repo:snowflakedb/container-images'
)
Security Scanning
# Vulnerability scanning
mcp_github_search_code(
query='scan OR vulnerability OR CVE repo:snowflakedb/container-images'
)
# Security policies
mcp_github_search_code(
query='securityPolicy OR compliance repo:snowflakedb/container-images'
)
🎯 Key Components
Build Tools
# Build scripts
mcp_github_search_code(
query='path:scripts build repo:snowflakedb/container-images'
)
# Makefile targets
mcp_github_search_code(
query='Makefile repo:snowflakedb/container-images'
)
🗺️ Directory Structure
container-images/
├── base-images/ # Base container images
├── release_configs/ # Release configurations
├── scripts/ # Build/deploy scripts
├── security/ # Security scanning
└── tests/ # Image tests
📊 Common Issues
# Build failures
mcp_github_search_code(
query='"build failed" OR "docker build" repo:snowflakedb/container-images'
)
# Registry push issues
mcp_github_search_code(
query='"push failed" OR registry 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.
- 5d ago First seen · 99 lines · 545 tokens per session scan A bbb007bdf5f8
container-images 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 545 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
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.