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 skills/googlecloudplatform/cortex-framework/data_modeling_standardsnpx skills add GoogleCloudPlatform/cortex-framework --skill data_modeling_standardsgit clone --depth 1 https://github.com/GoogleCloudPlatform/cortex-frameworkWhat 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 | $0.00026 | $0.01976 |
| Opus 5 | $0.00013 | $0.00988 |
| Sonnet 5 | $0.00005 | $0.00395 |
| Haiku 4.5 | $0.00003 | $0.00198 |
Grade A, and why
data_modeling_standards 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 2d 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 — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Data Modeling Standards and Business Rules
This skill serves as the single source of truth for organizational standards, naming conventions, and repeating data modeling patterns within the Cortex Framework. All agents creating or modifying data products MUST consult this guide to ensure consistency, design integrity, and compliance across the workspace.
1. Column Naming Conventions (Traceability)
In Cortex, column names must provide both business readability and technical traceability back to the source system.
- Rule: Target columns MUST be named in lowercase
snake_case. - Traceability Suffix: Column names MUST end with the original SAP field name as a suffix (e.g.,
_<sap_field_name>). - Examples:
mandt(Client) ->client_mandtbukrs(Company Code) ->company_code_bukrsbelnr(Accounting Document Number) ->document_number_belnrwaers(Currency Key) ->currency_key_waers
2. Currency Decimal Shifts
SAP stores currency amounts as integer/decimal values without decimals, shifting the actual values depending on the specific currency key (e.g., Japanese Yen JPY has 0 decimals, whereas USD has 2). We must adjust these amounts using the standard currency decimal shift configuration.
Implementation Checklist
- Require the Currency helper:
const currency = require("includes/cortex/currency.js"); - Define the
currency_decimalCTE at the top of the SQL query, passing the dataset reference for the replicatedtcurxtable:WITH currency_decimal AS ( ${currency.currencyDecimalShift(ctx.ref(moduleConfig.sources.sapModule.datasetId, "tcurx"))} ) - Apply the decimal shift expression to amount fields in the
SELECTblock:${currency.amountWithDecimalShift("bseg.dmbtr", "currency_decimal_hwaer")} AS amount_in_local_currency_dmbtr, ${currency.amountWithDecimalShift("bseg.wrbtr", "currency_decimal_waers")} AS amount_in_document_currency_wrbtr, - Join the
currency_decimalCTE in theFROM/JOINsection for each currency key:LEFT JOIN currency_decimal AS currency_decimal_waers ON bkpf.waers = currency_decimal_waers.currkey LEFT JOIN currency_decimal AS currency_decimal_hwaer ON bkpf.hwaer = currency_decimal_hwaer.currkey
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.
- 2d ago First seen · 166 lines · 26 tokens per session scan A 263654dd262f
data_modeling_standards is a skill published in the GitHub repository GoogleCloudPlatform/cortex-framework (10 stars, last pushed 6d ago), licensed Apache-2.0. It adds 26 tokens to every session and 1,976 once invoked, about $0.0001 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 skills, from other repositories
google-mobile-ads-android-migrate-to-next-gen
Migrates Android applications from the old, legacy Google Mobile Ads (GMA) SDK (com.google.android.gms:play-services-ads) to the new GMA Next-Gen SDK (com.google.android.libraries.ads.mobile.sdk:ads-mobile-sdk). Provides comprehensive mapping tables for imports, classes, and method signatures to help determine…
agent-platform-tuning
Agent Platform Model Tuning. Use when you need to fine-tune open models or Gemini models using Agent Platform infrastructure. Don't use for model training outside Agent Platform, model deployment to endpoints (use agent-platform-deploy), or managing serving endpoints (use agent-platform-endpoint-management).
application-design-center-design-deploy
Processes GCP infrastructure design and deployment workflows within Application Design Center (ADC). Use when: - Designing GCP infrastructure with Terraform. - Validating local HCL. - Performing best-practice plan scans. - Importing templates to Application Design Center (ADC). - Deploying templates. - Troubleshooting…
cloud-run-basics
Manages Cloud Run services, jobs, and worker pools. Use when you need to deploy applications responding to HTTP requests (services), run event-triggered or scheduled tasks (jobs), or handle always-on pull-based background processing (worker pools).
google-analytics-data-api-basics
Manages Google Analytics reporting data, enables the Analytics Data API via the Cloud CLI, and creates reports using the Google Analytics Data API (v1beta). Use when you need to interact with Google Analytics properties, run customized analytics reports, query metrics (like activeUsers, screenPageViews) and dimensions…
agent-platform-rag-engine-management
Manage and query Agent Platform RAG Engine Corpora and retrieve grounded contexts using the Google GenAI SDK. Use when listing RAG corpora or files, inspecting a corpus, retrieving contexts, or generating content grounded in a RAG corpus. Do not use for standard database queries (use SQL/Spanner skills), Google…