Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/twells89/sigma-skillsnpx agentmods add rules/twells89/sigma-skills/sigma-workbooksWrote 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-workbooks)<a href="https://agentmods.dev/rules/twells89/sigma-skills/sigma-workbooks"><img src="https://agentmods.dev/badge/rules/twells89/sigma-skills/sigma-workbooks/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-workbooks"><img src="https://agentmods.dev/badge/rules/twells89/sigma-skills/sigma-workbooks.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.00160 | $0.09136 |
| Opus 5.5 | $0.00064 | $0.03654 |
| Sonnet 5.5 | $0.00032 | $0.01827 |
| Haiku 4.5 | $0.00016 | $0.00914 |
Grade A, and why
sigma-workbooks 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 22d 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.
curl -sfL https://assets.sigmacomputing.com/openapi/public-rest-api/sigma-computing-public-rest-api.json \ How it starts
The opening of the file, as written. The whole thing — 496 lines — stays where its author put it; the contents beside it link to each section on GitHub.
sigma-workbooks
Build, edit, and iterate on Sigma workbook specs — the JSON definition you POST to /v2/workbooks/spec, covering pages, layout, controls, charts, KPIs, tables, formulas, and sources. The Sigma OpenAPI is the source of truth for every shape and field; this skill adds navigation, style guidance, and proven recipes for effective dashboards and operational apps. Use when the user wants to construct a dashboard from a spec, generate a Sigma app (planning, approval, allocation, or exception), reproduce a screenshot/mockup/Claude design artifact as a native Sigma app, add or modify pages / elements / controls / formulas, validate a spec before submission, or work through the workbook spec lifecycle programmatically. 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-workbooks/ (project install) or
~/.sigma-skills/sigma-workbooks/ (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 Workbooks (Spec via REST API)
This skill helps you build effective Sigma workbooks by navigating the Sigma OpenAPI and applying style guidance + proven recipes beyond what the OpenAPI alone teaches.
Scope
The workbook spec — the JSON you POST to /v2/workbooks/spec defining pages, elements, sources, formulas, and layout. Layout supports grid placement plus responsive stack containers. Lifecycle around the workbook (embeds, grants, materialization schedules, bookmarks, sharing) is a separate API surface and out of scope here.
Sources of truth
Sigma's public API docs are an index at https://help.sigmacomputing.com/openapi.json that lists two canonical split specs (split from one large spec to fix compilation / out-of-memory errors — so the structure changed subtly). That index now serves an HTML page, not JSON (verified 2026-08-05) — it renders links to the two specs rather than returning a machine-readable list, so treat it as a human landing page and go straight to the two URLs below:
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.
- 22d ago Changed · +3 lines 6698f631b383
- 24d ago Changed · +9 lines d17ce2ff5d1e
- 29d ago Changed a1531a6b948c
- 1mo ago Changed · +39 lines d993ae20088e
- 1mo ago Changed a74e9aa2c50b
- 1mo ago Changed · +17 lines 3d627da4ae91
- 2mo ago First seen · 428 lines · 160 tokens per session scan A b1bfa4c0d404
sigma-workbooks is a cursor rule published in the GitHub repository twells89/sigma-skills (16 stars, last pushed 14d ago), licensed Apache-2.0. It adds 160 tokens to every session and 9,136 once invoked, about $0.0006 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other cursor rules, from other repositories
read-xlsx
Reading, writing, diffing, and repairing spreadsheets (.xlsx) for AI agents via the xfa MCP server.
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.