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 skills add GoogleCloudPlatform/cortex-framework --skill setup_cortex_configgit clone --depth 1 https://github.com/GoogleCloudPlatform/cortex-frameworkWrote 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/skills/googlecloudplatform/cortex-framework/setup_cortex_config)<a href="https://agentmods.dev/skills/googlecloudplatform/cortex-framework/setup_cortex_config"><img src="https://agentmods.dev/badge/skills/googlecloudplatform/cortex-framework/setup_cortex_config/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/skills/googlecloudplatform/cortex-framework/setup_cortex_config"><img src="https://agentmods.dev/badge/skills/googlecloudplatform/cortex-framework/setup_cortex_config.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00036 | $0.01413 |
| Opus 5.5 | $0.00014 | $0.00565 |
| Sonnet 5.5 | $0.00007 | $0.00283 |
| Haiku 4.5 | $0.00004 | $0.00141 |
Grade A, and why
setup-cortex-config 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 1mo 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 — 118 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Setup Cortex Configuration
This skill assists in establishing, customizing, and validating the primary Cortex Framework configuration (config.yaml). It uses a slot-filling experience to ensure all mandatory and optional configurations are accurately populated, conforming to Google Cloud and BigQuery formatting requirements.
Required vs. Optional Configuration
Cortex V7 requires accurate environment details to coordinate BigQuery transformations and orchestrate Dataform pipelines.
1. Mandatory Configuration Settings (Strict Validation)
The following values MUST be populated with valid, non-placeholder values:
buildEnvironment.buildProjectId: The Google Cloud Project ID where build operations and script executions run.data.bigQueryLocation: The geographical location for BigQuery datasets (e.g.,US,EU,us-central1).data.sources: Needs at least one data source (typicallyid: sap_raw) mapping the replication source:projectId: GCP project ID hosting the raw/replicated SAP tables.datasetId: BigQuery dataset ID containing the replicated tables (e.g.,cortex_sap_raw).
data.targets: Needs target datasets where transformations will be materialized:- Foundation Target (
id: sap_foundation): Project ID and Dataset ID for processed, standard tables. - Product Target (
id: product_target): Project ID and Dataset ID for final data products.
- Foundation Target (
deployment.targets: Orchestration targets (Dataform repository setup):repositoryProjectId: GCP Project ID hosting the Dataform repository.repositoryRegion: GCP region hosting the repository (e.g.,us-central1).repositoryName: Unique repository name (e.g.,cortex-repository).workspaceName: Dataform workspace name (e.g.,dev).
2. Optional Configuration Settings
data.namespaces: Custom namespaces for data foundation and products (default iscortex). Note: defining a custom/customer namespace is NOT required for standard framework setup, and is only recommended/required when building the customer's own new or derived data products.modules.foundationssettings:sapVersion: Target SAP version (eccors4).mandt: 3-digit SAP client identifier (defaults to"100").enabled: Settrueorfalseto enable/disable specific foundations.tableSettings: File path override for custom table listings.
modules.productssettings:enabled: Settrueorfalseto build/deploy individual data products.tableSettings: Custom partitioning/clustering settings file path.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 118 lines · 36 tokens per session scan A 726a0bf3233c
setup-cortex-config is a skill published in the GitHub repository GoogleCloudPlatform/cortex-framework (14 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 36 tokens to every session and 1,413 once invoked, about $0.0001 per session on Opus 5.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
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).
google-cloud-solution-guided-gke-ai-migration
Guides the migration of existing AI workloads (Cloud Run, Gemini API, Gemini Enterprise Agent Platform) to self-hosted GKE inference using gcloud and kubectl. Use when the user has an existing AI inference workload (on Cloud Run, the Gemini API, Gemini Enterprise Agent Platform, or a custom VM) and wants to move it to…
agent-platform-endpoint-management
Manages Agent Platform serving endpoints. Use when you need to create, list, describe, update, or delete serving endpoints for model deployment on Agent Platform. Also use when troubleshooting endpoint permission, quota, or resource busy errors. Don't use for deploying models to endpoints or for running model…
gke-inference
Deploys and optimizes AI/ML inference workloads on GKE, using GPUs, TPUs, and model servers. Use when deploying GKE inference servers, configuring GKE GPU resources for inference, or deploying LLMs on GKE. Don't use for migrating existing AI workloads to GKE (use google-cloud-solution-guided-gke-ai-migration), GKE RAG…
tensorrt-llm
High-throughput LLM inference on NVIDIA GPUs.
gke-compute-classes
Configures, optimizes, and troubleshoots GKE ComputeClasses. Use when configuring Spot VMs with on-demand fallback, targeting specific accelerators (GPUs/TPUs) or machine families, restricting ComputeClass access, or debugging pending pods related to node pool auto-creation. Do not use for cluster-level Node Auto…