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/04-dpo-mappings)<a href="https://agentmods.dev/rules/sfc-gh-cconner/support-rules-mcp/04-dpo-mappings"><img src="https://agentmods.dev/badge/rules/sfc-gh-cconner/support-rules-mcp/04-dpo-mappings/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/04-dpo-mappings"><img src="https://agentmods.dev/badge/rules/sfc-gh-cconner/support-rules-mcp/04-dpo-mappings.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.04880 | $0.04880 |
| Opus 5 | $0.02440 | $0.02440 |
| Sonnet 5 | $0.00976 | $0.00976 |
| Haiku 4.5 | $0.00488 | $0.00488 |
Grade A, and why
04-dpo-mappings 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 — 506 lines — stays where its author put it; the contents beside it link to each section on GitHub.
DPO to Snowhouse Table Mappings
PURPOSE: Authoritative mapping of Snowflake Data Persistence Objects (DPOs) to Snowhouse ETL views.
🚨 MOST IMPORTANT RULE
NOT ALL OBJECTS HAVE DEDICATED TABLES!
Stage-Backed Objects ALL go to stage_etl_v:
- ❌ WRONG:
image_repository_etl_v(doesn't exist!) - ✅ RIGHT:
stage_etl_vwithstage_type = 'IMAGE_REPOSITORY'
This is the #1 source of confusion in Snowhouse investigations.
📊 Complete DPO Mapping Table
Core Database Objects
| Object Type | DPO Name | Snowhouse Table | Key Fields |
|---|---|---|---|
| Account | accountDPO |
account_etl_v |
account_id, account_locator |
| Database | databaseDPO |
database_etl_v |
database_id, database_name |
| Schema | schemaDPO |
schema_etl_v |
schema_id, schema_name, database_id |
| Table | tableDPO |
table_etl_v |
table_id, table_name |
| View | viewDPO |
view_etl_v |
view_id, view_name |
| Column | columnDPO |
column_etl_v |
column_id, table_id |
| Sequence | sequenceDPO |
sequence_etl_v |
sequence_id, sequence_name |
| Function | functionDPO |
function_etl_v |
function_id, function_name |
| Procedure | procedureDPO |
procedure_etl_v |
procedure_id, procedure_name |
| File Format | fileFormatDPO |
file_format_etl_v |
file_format_id, file_format_name |
| Pipe | pipeDPO |
pipe_etl_v |
pipe_id, pipe_name |
| Stream | streamDPO |
stream_etl_v |
stream_id, stream_name |
🚨 Stage-Backed Objects (ALL USE stage_etl_v)
| Object Type | DPO Name | Snowhouse Table | Filter Required | Stage Type |
|---|---|---|---|---|
| Stage (all types) | stageDPO |
stage_etl_v |
No (all types) | All |
| Image Repository | imageRepositoryDPO |
stage_etl_v |
YES | stage_type = 'IMAGE_REPOSITORY' |
| Git Repository | gitRepositoryDPO |
stage_etl_v |
YES | stage_type = 'GIT_REPOSITORY' |
| Internal Stage | internalStageDPO |
stage_etl_v |
Yes | stage_type = 'INTERNAL' |
| External Stage | externalStageDPO |
stage_etl_v |
Yes | stage_type IN ('S3', 'AZURE', 'GCS') |
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 · 506 lines · 4,880 tokens per session scan A 51d6b98cedbb
04-dpo-mappings 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 4,880 tokens to every session, about $0.0244 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.