Borrowing it
Nothing to install: this file belongs to mendix/web-widgets. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/mendix/web-widgets/main/.agents/skills/debug-widget/SKILL.mdgit clone --depth 1 https://github.com/mendix/web-widgetsWrote 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/mendix/web-widgets/debug-widget)<a href="https://agentmods.dev/skills/mendix/web-widgets/debug-widget"><img src="https://agentmods.dev/badge/skills/mendix/web-widgets/debug-widget/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/mendix/web-widgets/debug-widget"><img src="https://agentmods.dev/badge/skills/mendix/web-widgets/debug-widget.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium MCP Rug Pull · line 43 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium MCP Rug Pull · line 101 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
- medium Prompt Injection · line 150 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
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.00037 | $0.01917 |
| Opus 5.5 | $0.00015 | $0.00767 |
| Sonnet 5.5 | $0.00007 | $0.00383 |
| Haiku 4.5 | $0.00004 | $0.00192 |
Grade A, and why
debug-widget 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 1mo 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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debug Widget
Overview
Evidence-first debugging for Mendix pluggable widgets. You MUST reproduce the bug with Playwright before reading source code, and MUST verify the fix with Playwright before declaring success.
REQUIRED BACKGROUND: superpowers:systematic-debugging for general root-cause methodology.
Prerequisites
Before starting, confirm with the user:
- Test project running? The Mendix app must be live at
http://localhost:8080. Ask: "Is the Studio Pro project running?" - MX_PROJECT_PATH set? Needed for deploying the built widget. Ask if not provided.
- JIRA/bug description? Extract: widget package, symptom, reproduction steps.
Workflow
Phase 1: Reproduce
-
Identify the target from the bug report:
- Widget package (
combobox-web,datagrid-web, …) - Symptom type — see Bug Categories table below
- Reproduction steps from JIRA
- Widget package (
-
Find the page — see page-discovery.md
-
Write a diagnostic Playwright script that follows the JIRA reproduction steps and captures the symptom as a measurable assertion or console output diff.
See diagnostic-patterns.md for templates by bug category.
Save it as:
packages/pluggableWidgets/<widget>-web/e2e/<bug-id>-diagnostic.spec.js -
Run it:
cd packages/pluggableWidgets/<widget>-web npx playwright test e2e/<bug-id>-diagnostic.spec.js --headed -
Confirm reproduction:
- Script shows wrong values / assertion fails → proceed to Phase 2
- Script does NOT demonstrate the bug → fix the script (selectors, timing, page URL). Do NOT proceed to Phase 2 until the script confirms the symptom.
Phase 2: Analyze + Fix
Now you may read source code.
- Trace the reactive chain from DOM symptom to root cause.
See reactive-chain.md.
- Simple widgets (combobox, badge): React props → hooks → component render
- Complex widgets (datagrid, gallery): React props → Gate → MobX stores → Observer components
What ships with it
3 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.
- 1mo ago First seen · 167 lines · 37 tokens per session scan A 6fa5c0ce020d
debug-widget is a skill published in the GitHub repository mendix/web-widgets (40 stars, last pushed today), licensed Apache-2.0. It adds 37 tokens to every session and 1,917 once invoked, about $0.0001 per session on Opus 5.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-09-01.
Other skills, from other repositories
wick-html-widget
Use when an HTML artifact / widget preview in wick chat misbehaves — blank or clipped iframe, "violates the following Content Security Policy directive", a stylesheet or script that never loads, images blocked by img-src, a slide deck whose navigation is dead, or a preview that needs to read a session file. Covers the…
chrome-devtools-cli
Use this skill to write shell scripts or run shell commands to automate tasks in the browser or otherwise use Chrome DevTools via CLI.
a11y-debugging
Uses Chrome DevTools MCP for accessibility (a11y) debugging and auditing based on web.dev guidelines. Use when testing semantic HTML, ARIA labels, focus states, keyboard navigation, tap targets, and color contrast.
chrome-devtools
Uses Chrome DevTools via MCP for efficient debugging, troubleshooting and browser automation. Use when debugging web pages, automating browser interactions, analyzing performance, or inspecting network requests. This skill does not apply to --slim mode (MCP configuration).
opencli-autofix
Automatically fix broken OpenCLI adapters when commands fail. Load this skill when an opencli command fails — it guides you through collecting a trace artifact, patching the adapter, retrying, and filing an upstream GitHub issue after a verified fix. Works with any AI agent.
chrome-performance-optimizer
Autonomous multi-agent performance optimization loop for Chromium and V8. Supports profile-seeded mode (analyzing Speedometer 3 / JetStream profiles via pprof or Sagacity MCP) and pattern-driven discovery mode (fan-out exploration of Blink and V8 macro-patterns grounded in historical wins and past rejected CLs).…