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-migration-skillsnpx agentmods add skills/twells89/sigma-migration-skills/domo-assessmentWrote 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-assessment)<a href="https://agentmods.dev/skills/twells89/sigma-migration-skills/domo-assessment"><img src="https://agentmods.dev/badge/skills/twells89/sigma-migration-skills/domo-assessment/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-assessment"><img src="https://agentmods.dev/badge/skills/twells89/sigma-migration-skills/domo-assessment.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.00101 | $0.03250 |
| Opus 5 | $0.00051 | $0.01625 |
| Sonnet 5 | $0.00020 | $0.00650 |
| Haiku 4.5 | $0.00010 | $0.00325 |
Grade A, and why
domo-assessment 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 12d 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 — 211 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Domo Assessment
STATUS: offline-complete (hermetic fixture pipeline, both governance tiers); live not yet validated. The four pipeline scripts run end-to-end against committed Tier A / Tier B fixtures (
bash run-offline.sh) and the repo test suite. What remains live: confirming the exact governance-dataset names/column schemas on first contact with a real Domo instance (see "Open work" below) — this skill defers that, consistent with this repo's rule of never calling something validated until it's proven live.
Read first:
refs/governance-datasets.md— which Governance/DomoStats system datasets power which section, the SQL query pattern, and the offline fixture filenamesrefs/complexity-scoring.md— the Domo convertibility rubric (Beast Mode bucketing + card-type coverage + structural flags)refs/output-shapes.md— exact JSON shapes each stage reads/writesrefs/readout-template.md— thereadout.mdsection layout../domo-to-sigma/SKILL.md— the conversion skill this feeds into; auth recipe
The key idea
Domo's admin-installable DomoStats and Governance Datasets connectors
materialize the instance's own metadata (DataSets, DataFlows, Pages, Cards,
Users, PDP policies, Activity Log) as ordinary DataSets — queryable via the
public, documented POST /v1/datasets/query/execute/{id} endpoint with
plain MySQL SQL. That's Domo's analog of Tableau Admin Insights: no
private-API scraping is required just to build an inventory. Card-level Beast
Mode SQL text (the real complexity signal) is only visible either through a
DOMO_DEV_TOKEN against the private card-definition API, or — on instances
where it's installed — through a public Beast Modes governance dataset.
Whichever is reachable determines the assessment's tier:
- Tier A — Beast Mode SQL is visible. Every card's Beast Modes are
bucketed auto/manual/unhandled (same
convert_sql_to_sigma_formulacoverage rulesdomo-to-sigmauses) and folded into cost/score. - Tier B — public API only. Beast Mode buckets are forced to zero; cost/
score are driven by structural flags (PDP, DataFlow-sourced) and usage only.
The shortlist is directional, not precise (see
refs/complexity-scoring.md§4).
What ships with it
41 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.
- fixtures/tier-a/activity-log.json 1.7 KB
- fixtures/tier-a/beast-modes.json 581 B
- fixtures/tier-a/card-defs.json 1.0 KB
- fixtures/tier-a/cards.json 1.2 KB
- fixtures/tier-a/dataflows.json 363 B
- fixtures/tier-a/datasets.json 767 B
- fixtures/tier-a/pages.json 289 B
- fixtures/tier-a/pdp.json 334 B
- fixtures/tier-a/users.json 1.0 KB
- fixtures/tier-b/activity-log.json 1.7 KB
- fixtures/tier-b/cards.json 894 B
- fixtures/tier-b/dataflows.json 363 B
- fixtures/tier-b/datasets.json 767 B
- fixtures/tier-b/pages.json 289 B
- fixtures/tier-b/pdp.json 334 B
- fixtures/tier-b/users.json 1.0 KB
- PRIVACY.md 4.8 KB
- README.md 2.8 KB
- refs/complexity-scoring.md 7.0 KB
- refs/governance-datasets.md 4.5 KB
- refs/output-shapes.md 7.6 KB
- refs/readout-template.md 5.1 KB
- run-offline.sh 1.8 KB runs code
- scripts/bootstrap.ps1 38 KB runs code
- scripts/bootstrap.sh 41 KB runs code
- scripts/discover-domo.rb 12 KB runs code
- scripts/doctor.ps1 19 KB runs code
- scripts/doctor.sh 27 KB runs code
- scripts/dup-dashboards.py 13 KB runs code
- scripts/probe-governance.rb 6.9 KB runs code
- scripts/render-readout.rb 9.0 KB runs code
- scripts/score-coverage.rb 9.5 KB runs code
- test/helper.rb 349 B runs code
- test/test-discover-malformed.rb 1.6 KB runs code
- test/test-discover.rb 708 B runs code
- test/test-fixtures.rb 2.3 KB runs code
- test/test-helper.rb 219 B runs code
- test/test-probe.rb 670 B runs code
- test/test-render.rb 694 B runs code
- test/test-score-noaudit.rb 2.0 KB runs code
- test/test-score.rb 1.1 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.
- 12d ago First seen · 211 lines · 101 tokens per session scan A 370b64808c21
domo-assessment is a skill published in the GitHub repository twells89/sigma-migration-skills (16 stars, last pushed yesterday), licensed MIT. It adds 101 tokens to every session and 3,250 once invoked, about $0.0005 per session on Opus 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…