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 twells89/sigma-migration-skills --skill domo-import-to-snowflakegit clone --depth 1 https://github.com/twells89/sigma-migration-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/skills/twells89/sigma-migration-skills/domo-import-to-snowflake)<a href="https://agentmods.dev/skills/twells89/sigma-migration-skills/domo-import-to-snowflake"><img src="https://agentmods.dev/badge/skills/twells89/sigma-migration-skills/domo-import-to-snowflake/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/twells89/sigma-migration-skills/domo-import-to-snowflake"><img src="https://agentmods.dev/badge/skills/twells89/sigma-migration-skills/domo-import-to-snowflake.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.00000 | $0.01431 |
| Opus 5.5 | $0.00000 | $0.00572 |
| Sonnet 5.5 | $0.00000 | $0.00286 |
| Haiku 4.5 | $0.00000 | $0.00143 |
Grade A, and why
domo-import-to-snowflake 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 2mo 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Domo (landed data) → Snowflake
Sigma is warehouse-native: every DM table resolves as live SQL against a
connected warehouse. domo-to-sigma's build-dm.rb already knows how to
auto-fill discovery/dataset-map.json for connector-backed DataSets (Domo's
own Snowflake connector carries databaseName/schemaName/tableName in
its stream config), but a DataSet landed directly into Domo — API, webform,
Excel upload, or Domo's own sample/demo content — has no warehouse table at
all. build-dm.rb flags this rather than guessing: the entry gets
_source: "domo-landed-data" and an unmistakable sentinel table name,
<TABLE:LANDED_DATA_NO_WAREHOUSE_SOURCE>. This skill extracts that DataSet's
rows and lands them in Snowflake, then patches the entry in place so the very
next build-dm.rb run resolves it like any other DataSet.
Two tracks, one migration (this skill is track 1):
1. DATA (this skill) domo-landed-data DataSets → Snowflake tables + dataset-map.json patched
2. LOGIC (domo-to-sigma) Beast Modes / cards / layout → Sigma dashboard — unchanged
Track 2 needs no separate repoint step: build-dm.rb already reads
dataset-map.json directly, so once this skill patches an entry, the next
build-dm.rb/migrate-domo.rb run just works.
Skip this skill for connector-backed DataSets — they already resolve via
build-dm.rb's existing stream-config auto-fill.
What it does
scripts/domo_import_to_snowflake.rb (generic — no hardcoded dataset ids):
- Select — reads the sibling
domo-to-sigmaskill'sdiscovery/dataset-map.json; auto-detects every_source: "domo-landed-data"entry, or takes an explicit--dataset-idsubset. - Extract + schema —
Domo.query_dataset(id, sql), paginated explicitly, with a measuredCOUNT(*)row-count parity check (never assumed). Column types come from the same response'smetadata[].type(paired positionally withcolumns), notDomo.dataset(id)['schema']— live validation found that field empty for 9 of 10 real sample DataSets. Seerefs/type-mapping.mdfor the Domo → Snowflake type table andrefs/live-validation.mdfor what was confirmed live. - Load — typed
CREATE TABLE+snow sqlPUT/COPY INTO, then aGRANT SELECT(default rolePUBLIC, overridable). - Sync —
--sigma-connection <uuid>triggersPOST /v2/connections/<id>/synconce after the whole batch, so new tables resolve immediately. - Patch — rewrites the landed entries'
database/schema/tableand_sourceindataset-map.json(seerefs/naming-and-sentinel.md).connectionIdis never touched — same rule as every other entry type.
What ships with it
15 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.
- PRIVACY.md 1007 B
- README.md 1.1 KB
- refs/live-validation.md 4.4 KB
- refs/naming-and-sentinel.md 1.9 KB
- refs/type-mapping.md 1.3 KB
- scripts/domo_import_to_snowflake.rb 8.0 KB runs code
- scripts/lib/domo_extract.rb 4.6 KB runs code
- scripts/lib/landing_manifest.rb 1.3 KB runs code
- scripts/lib/snowflake_ddl.rb 2.8 KB runs code
- scripts/lib/snowflake_load.rb 4.6 KB runs code
- test/test-domo-extract.rb 8.5 KB runs code
- test/test-landing-manifest.rb 2.0 KB runs code
- test/test-sigma-sync.rb 704 B runs code
- test/test-snowflake-ddl.rb 3.0 KB runs code
- test/test-snowflake-load.rb 4.8 KB runs code
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.
- 2mo ago First seen · 97 lines · 0 tokens per session scan A 60112920c5f1
domo-import-to-snowflake is a skill published in the GitHub repository twells89/sigma-migration-skills (18 stars, last pushed 18d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,431 tokens. 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-30.
domo-import-to-snowflake compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| domo-import-to-snowflaketwells89/sigma-migration-skills | Skill | 18 | 18d ago | MIT | A | 0 | Claude Code |
| embeddingsruvnet/ruflo | Skill | 81k | today | MIT | A | 62 | Claude Code |
| rag-pineconedavila7/claude-code-templates | Skill | 33k | today | MIT | A | 65 | Claude Code, Codex |
| data-engineerdavila7/claude-code-templates | Skill | 33k | today | MIT | A | 35 | Claude Code, Codex |
| similarity-search-patternsforyourhealth111-pixel/Vibe-Skills | Skill | 3.8k | yesterday | Apache-2.0 | A | 30 | Claude Code, Codex |
| ingesting-into-data-lakeaws/agent-toolkit-for-aws | Skill | 3.4k | today | Apache-2.0 | A | 228 | Claude Code |
| graphjin-envdosco/graphjin | Skill | 3.2k | 3d ago | Apache-2.0 | A | 61 | Claude Code, Codex |