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/07-mono-repo-structure)<a href="https://agentmods.dev/rules/sfc-gh-cconner/support-rules-mcp/07-mono-repo-structure"><img src="https://agentmods.dev/badge/rules/sfc-gh-cconner/support-rules-mcp/07-mono-repo-structure/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/07-mono-repo-structure"><img src="https://agentmods.dev/badge/rules/sfc-gh-cconner/support-rules-mcp/07-mono-repo-structure.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.02484 | $0.02484 |
| Opus 5 | $0.01242 | $0.01242 |
| Sonnet 5 | $0.00497 | $0.00497 |
| Haiku 4.5 | $0.00248 | $0.00248 |
Grade A, and why
07-mono-repo-structure 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 9d 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 — 306 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Snowflake Mono Repo Structure Guide
PURPOSE: Detailed guide to Snowflake mono repo organization and code navigation patterns.
📁 Top-Level Structure
snowflake/ (GitHub: snowflakedb/snowflake)
├── GlobalServices/ # Frontend services (GS)
├── ExecPlatform/ # Backend execution (XP)
├── CloudServices/ # Cloud provider integrations
├── Storage/ # Storage layer and file formats
├── Security/ # Security and access control
├── DPO/ # Data Persistence Objects
├── API/ # Public APIs and interfaces
├── Common/ # Shared utilities and libraries
├── Tests/ # Test infrastructure
└── Scripts/ # Build and deployment scripts
Note: Snowsight and other Snowflake web applications live in a separate Snapps repository at GitHub: snowflakedb/snapps. For UI investigations, see the Snapps connector rule.
🎯 Key Component Details
GlobalServices (GS)
GlobalServices/
├── Auth/ # Authentication & authorization
├── Catalog/ # Metadata catalog service
├── Compiler/ # SQL compilation & optimization
├── Gateway/ # Request routing & load balancing
├── QueryHistory/ # Query history tracking
└── Session/ # Session management
Key Classes:
AuthenticationService- User authenticationCatalogService- Metadata operationsQueryCompiler- SQL → execution planRequestRouter- Routes queries to XP
Snowhouse Mapping: snowhouse_import.<deployment>.gs_logs_v
ExecPlatform (XP)
ExecPlatform/
├── Engine/ # Query execution engine
├── Warehouse/ # Virtual warehouse management
├── Task/ # Task scheduling & execution
├── Stream/ # Streams & CDC
├── Storage/ # Storage operations
└── Worker/ # Worker node management
Key Classes:
QueryExecutor- Main execution coordinatorWarehouseManager- VW lifecycleTaskScheduler- Task orchestrationStreamProcessor- CDC processing
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.
- 9d ago First seen · 306 lines · 2,484 tokens per session scan A 21ab76287f6b
07-mono-repo-structure 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 2,484 tokens to every session, about $0.0124 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
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.
cli-error-handling
CLI command error handling patterns.
prefer-direct-imports-over-module-mocks
Prefer extracting a testable core over vi.mock / vi.resetModules when unit tests need to reach production logic entangled with config, env, or singletons.
control-plane-descriptors
Control plane descriptor and instance implementation patterns.