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-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/plugins/twells89/sigma-migration-skills/domo-to-sigma)<a href="https://agentmods.dev/plugins/twells89/sigma-migration-skills/domo-to-sigma"><img src="https://agentmods.dev/badge/plugins/twells89/sigma-migration-skills/domo-to-sigma/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/plugins/twells89/sigma-migration-skills/domo-to-sigma"><img src="https://agentmods.dev/badge/plugins/twells89/sigma-migration-skills/domo-to-sigma.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
domo-to-sigma 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 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.
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.
What it actually says
{
"$schema": "https://json.schemastore.org/claude-code-plugin-manifest.json",
"name": "domo-to-sigma",
"displayName": "Domo \u2192 Sigma",
"version": "0.16.160",
"description": "Migrate Domo dashboards to Sigma \u2014 DataSets \u2192 Sigma data model (flat materialized tables \u2192 table elements), Beast Mode calc fields \u2192 Sigma formulas (MySQL-dialect SQL via the shared SQL-formula converter), and cards \u2192 charts/KPIs/pivots (every card's Summary Number \u2192 a Sigma KPI, not a table). Ports page + card filters as controls, detects PDP policies for opt-in row-level security, pre-flights Domo dataset columns against the real warehouse schema before building the data model, and defers live parity verification. Bundles a read-only domo-assessment skill (public governance-dataset inventory \u2192 value/cost-ranked migration-readiness readout) and domo-import-to-snowflake for landing DataSets with no connector-backed warehouse source. Companion to the sigma-migration-skills converters.",
"author": {
"name": "Thomas Wells"
},
"license": "MIT",
"keywords": [
"domo",
"beast-mode",
"sigma",
"migration",
"bi",
"converter",
"assessment"
],
"skills": "./skills/"
}
What it installs
The manifest is a name and a version. 3 skills travel with it, and installing the plugin installs all of them — 223 tokens a session between them. Each is measured on its own page, and each can be installed alone.
What ships with it
1 file beside plugin.json 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.
- 24d ago Changed b72187a1e390
- 1mo ago Changed ec4202122b49
- 1mo ago Changed 8b9d3087b33e
- 1mo ago Changed b0213074eaee
- 1mo ago Changed a74217bc047d
- 1mo ago Changed 3b817ee8da11
- 1mo ago Changed c530a5a4e934
- 1mo ago Changed 185b866d5881
- 1mo ago Changed 0f2cd0b9e151
- 1mo ago First seen · 22 lines scan A 3b1273ce8864
domo-to-sigma is a plugin published in the GitHub repository twells89/sigma-migration-skills (18 stars, last pushed 18d ago), licensed MIT. Its token cost is not measured: this kind of file is read by the harness, not the model. 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-to-sigma compared with plugins from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| domo-to-sigmatwells89/sigma-migration-skills | Plugin | 18 | 18d ago | MIT | A | — | Claude Code |
| humanizerblader/humanizer | Plugin | 67k | 13d ago | MIT | A | — | Claude Code |
| claude-plugins-official marketplaceanthropics/claude-plugins-official | Plugin | 47k | today | Apache-2.0 | A | — | Claude Code |
| nextjsvercel/next.js | Plugin | 143k | today | MIT | A | — | Claude Code |
| themes-examplegoogle-gemini/gemini-cli | Plugin | 109k | today | Apache-2.0 | A | — | Gemini CLI |
| knowledge-work-plugins marketplaceanthropics/knowledge-work-plugins | Plugin | 35k | 3d ago | Apache-2.0 | A | — | Claude Code |
| code-modernizationanthropics/claude-plugins-official | Plugin | 47k | today | Apache-2.0 | A | — | Claude Code |