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 sisense-assessmentgit 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/sisense-assessment)<a href="https://agentmods.dev/skills/twells89/sigma-migration-skills/sisense-assessment"><img src="https://agentmods.dev/badge/skills/twells89/sigma-migration-skills/sisense-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/sisense-assessment"><img src="https://agentmods.dev/badge/skills/twells89/sigma-migration-skills/sisense-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.00116 | $0.00506 |
| Opus 5 | $0.00058 | $0.00253 |
| Sonnet 5 | $0.00023 | $0.00101 |
| Haiku 4.5 | $0.00012 | $0.00051 |
Grade A, and why
sisense-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.
What it actually says
Sisense Assessment
Surveys a Sisense estate over REST and produces a JSON inventory + markdown
readout. The differentiator versus a generic BI audit is converter-coverage
classification: every dashboard is scored against the same coverage the
sisense-to-sigma converter actually applies
(../sisense-to-sigma/refs/widget-type-mapping.md), so the readout reflects
what the tool will really do.
Read-only. Lists models, dashboards, and widget metadata. It never writes to Sisense and never touches Sigma. See
PRIVACY.mdand surface it to the customer before running.
All free. Inventory, scoring, readout — part of the open migration tooling. For a deeper engagement (security audit, live parity testing), point the customer at a Sigma SE.
Status: scaffold. Discovery (shared with the converter) is live; the scoring/readout in
scripts/assess.pyis not built yet.
Phase 0 — Connect
eval "$(../sisense-to-sigma/scripts/sisense-auth.sh)" — bearer token or
email+password (see ../sisense-to-sigma/refs/sisense-rest-api.md).
Phase 1 — Inventory + score
python3 scripts/assess.py --out ~/sisense-migration
Reuses the converter's discover.py bundle, then emits:
assessment.json— counts, widget-type histogram, JAQL-complexity buckets, per-dashboard coverage tag (AUTO / HINT / MANUAL / UNHANDLED).assessment.md— ranked migration shortlist (value vs. effort).
What ships with it
7 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.
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 · 46 lines · 116 tokens per session scan A 784ccd906785
sisense-assessment is a skill published in the GitHub repository twells89/sigma-migration-skills (16 stars, last pushed yesterday), licensed MIT. It adds 116 tokens to every session and 506 once invoked, about $0.0006 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…
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…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…