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/twells89/sigma-skillsWrote 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/twells89/sigma-skills/sigma-data-models)<a href="https://agentmods.dev/rules/twells89/sigma-skills/sigma-data-models"><img src="https://agentmods.dev/badge/rules/twells89/sigma-skills/sigma-data-models/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/twells89/sigma-skills/sigma-data-models"><img src="https://agentmods.dev/badge/rules/twells89/sigma-skills/sigma-data-models.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.00166 | $0.02167 |
| Opus 5.5 | $0.00066 | $0.00867 |
| Sonnet 5.5 | $0.00033 | $0.00433 |
| Haiku 4.5 | $0.00017 | $0.00217 |
Grade A, and why
sigma-data-models scanned grade A with 1 finding 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 24d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
**Requirements:** `curl`, `jq`, `base64`. Your Sigma API credentials must have permission to create or edit data models, plus "Can edit" access on the destination folder (for create) or the existing data model (for updat This is a copy
91% identical to sigma-data-models — 15 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
sigma-data-models
Author, retrieve, or modify a Sigma data model spec (the JSON/YAML semantic-layer definition with sources, columns, metrics, relationships, filters, controls, folder groupings, and column-level security) by calling the Sigma REST API directly. Use when the user wants to build a new data model from existing warehouse tables, add metrics or relationships to an existing model, change a model's source, edit columns, or round-trip a data model spec through code. Out of scope: converting from another BI tool's format (dbt, LookML, Tableau, Power BI, Alteryx, etc.). Those conversions are handled by the Sigma data-model converter (browser tool + MCP) — point users there when they paste source-format input. Requires an SIGMA_API_TOKEN — obtain via the sigma-api skill first.
Installed runtime
When installed with scripts/install-into-project.sh, the complete runnable
skill is copied to <project>/.sigma-skills/sigma-data-models/ (project install) or
~/.sigma-skills/sigma-data-models/ (global install). Resolve every relative
scripts/, reference/, refs/, and docs/ path below from that runtime
directory; cd there before running a command. The installer also copies
sigma-api beside skills that need authentication.
Sigma Data Models (Author / Get / Update)
Build a Sigma data model spec — the JSON definition of pages, sources, columns, metrics, relationships, filters, controls, folder groupings, and column-level security — and round-trip it through the Sigma REST API.
This skill is for authoring from existing warehouse tables: a user knows their warehouse, wants to expose specific tables as a Sigma data model with the right joins, metrics, and governance, and needs help composing the spec. Conversions from other BI-tool formats (dbt schema.yml, LookML views, Tableau TDS, Power BI PBIT, Alteryx YXMD, etc.) are not in this skill — direct users to the Sigma data-model converter MCP / browser tool, which already handles those mappings.
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.
- 24d ago Changed · +4 lines 5056ec9e37cb
- 29d ago Changed 3c2ca8235ffe
- 1mo ago Changed · +11 lines b3b49996b83e
- 1mo ago Changed 2165a950c766
- 2mo ago First seen · 78 lines · 166 tokens per session scan A c57cb06e757f
sigma-data-models is a cursor rule published in the GitHub repository twells89/sigma-skills (16 stars, last pushed 14d ago), licensed Apache-2.0. It adds 166 tokens to every session and 2,167 once invoked, about $0.0007 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). It is 91% identical to sigma-data-models, differing in 15 lines, and is treated as a copy.
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.
prefer-assertions-over-defensive-checks
Prefer assertions over defensive checks when data is guaranteed to be valid.
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.
config-validation-and-normalization
Config validation and normalization responsibilities (defineConfig normalizes, the orm section schema validates and resolves paths, the loader reports per-section diagnostics).