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/metabase-to-sigma)<a href="https://agentmods.dev/plugins/twells89/sigma-migration-skills/metabase-to-sigma"><img src="https://agentmods.dev/badge/plugins/twells89/sigma-migration-skills/metabase-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/metabase-to-sigma"><img src="https://agentmods.dev/badge/plugins/twells89/sigma-migration-skills/metabase-to-sigma.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
metabase-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 11d 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": "metabase-to-sigma",
"displayName": "Metabase → Sigma",
"version": "0.1.7",
"description": "Migrate Metabase models, questions, and dashboards to Sigma data models and workbooks. Translates MBQL/pMBQL, remodels compatible native SQL, preserves controls and grid layout, verifies parity, and bundles a read-only estate assessment.",
"author": {
"name": "Thomas Wells"
},
"license": "MIT",
"keywords": [
"metabase",
"mbql",
"sigma",
"migration",
"bi",
"converter"
],
"skills": "./skills/"
}
What it installs
The manifest is a name and a version. 2 skills travel with it, and installing the plugin installs all of them — 220 tokens a session between them. Each is measured on its own page, and each can be installed alone.
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.
- 11d ago Changed e0c402375159
- 23d ago Changed d155b77f2ac6
- 29d ago Changed 24df4abf609a
- 1mo ago Changed e7798d7dfb92
- 1mo ago Changed ad78593044d1
- 1mo ago First seen · 21 lines scan A 19bf30758528
metabase-to-sigma is a plugin published in the GitHub repository twells89/sigma-migration-skills (17 stars, last pushed yesterday), 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-09-10.
Other plugins, from other repositories
before-you-build
Pre-build product risk review for founders, product teams, and AI-assisted builders before implementation starts.
obw
Obsidian Workspace — project-scoped vault productivity (capture / notes / PM). Skills own folder layout and templates; /obw:pm splits a spec into blocking tickets; /issue is a Claude Mod pane that lists a view of the project's dashboard, draws Mermaid as text diagrams, and can open a card in the browser through viz.…
feature-to-pr-factory
Turn one feature into dependency-ordered GitHub or GitLab issues, then build each ticket into its own reviewed, tested PR or MR with agents.
mission-control
SDLC management for Operations, Asgard, and CAMPPS: prepared issue drafts, live schema sync, board schemas, labels, project fields, metrics, and card validation.
feishu-calendar
Manage Feishu (Lark) calendar events — create, read, update, delete events and manage attendees via the Feishu Open Platform Calendar API v4.
gse
GSE-One — AI engineering companion for structured SDLC management. 24 commands, adaptive risk analysis, unified backlog, knowledge transfer, worktree isolation.