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 agentmods add skills/redhatinsights/nxtcm-components/monaco-component-testingnpx skills add RedHatInsights/nxtcm-components --skill monaco-component-testinggit clone --depth 1 https://github.com/RedHatInsights/nxtcm-componentsWrote 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/redhatinsights/nxtcm-components/monaco-component-testing)<a href="https://agentmods.dev/skills/redhatinsights/nxtcm-components/monaco-component-testing"><img src="https://agentmods.dev/badge/skills/redhatinsights/nxtcm-components/monaco-component-testing.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00019 | $0.04809 |
| Opus 5 | $0.00010 | $0.02405 |
| Sonnet 5 | $0.00004 | $0.00962 |
| Haiku 4.5 | $0.00002 | $0.00481 |
Grade A, and why
monaco-component-testing 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 4d 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 — 744 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Monaco Editor Component Testing Guide
Comprehensive guide for testing Monaco editor components in Playwright Component Tests (CT), including known limitations, testing strategies, and best practices learned from YAML editor implementation.
When to Use This Skill
Invoke this skill when:
- Testing components that use Monaco editor (CodeEditor, YAML editor, etc.)
- Planning test strategy for Monaco integration
- Debugging flaky Monaco tests
- Understanding why validation tests fail in CT
- Deciding which layer to test Monaco functionality
Related skills:
.agents/skills/monaco-e2e-testing/SKILL.md- E2E testing for Monaco (different constraints)
Critical Monaco Testing Limitations
Limitation 1: setValue() Does NOT Trigger onChange
The Problem:
Monaco's setValue() method does not fire the onChange event that validation logic depends on.
// ❌ This DOES NOT work in Playwright CT
await monacoEditor.evaluate((node) => {
const editor = (window as any).monacoEditor;
editor.setValue(invalidYaml); // onChange NOT triggered!
});
// Validation handler NEVER fires
// Error markers NEVER appear
// Error banner NEVER displays
Impact:
- Cannot test validation logic via Monaco in CT
- Cannot test error markers appearing in editor
- Cannot test error banner display
- Cannot test debounced validation
Solution: Test validation logic separately in unit tests (see Testing Strategy below)
Limitation 2: Complex DOM Structure Causes Click Interception
The Problem: Monaco creates multiple overlapping DOM layers (editor, overlays, minimap, margins) that intercept click events.
// ❌ These clicks are FLAKY in CT
await component.locator('.monaco-editor').click(); // Intercepted by overlay
await component.locator('button').click(); // Intercepted by editor
await component.locator('.monaco-editor textarea').click(); // Intercepted by margin
Playwright Error:
<div>…</div> from <div class="margin">…</div> subtree intercepts pointer events
<body>…</body> intercepts pointer events
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.
- 4d ago First seen · 744 lines · 19 tokens per session scan A b476d4a53d8d
monaco-component-testing is a skill published in the GitHub repository RedHatInsights/nxtcm-components (3 stars, last pushed 2d ago), licensed Apache-2.0. It adds 19 tokens to every session and 4,809 once invoked, about $0.0001 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-31.
Other skills, from other repositories
use-agent-browser-for-airi
Test AIRI display-model imports with agent-browser across stage-tamagotchi Electron, stage-web, and stage-pocket mobile web layouts. Use when uploading and verifying contributor-supplied Live2D ZIP, VRM, or MMD ZIP/PMX/PMD files through AIRI's model selector, including onboarding bypass, format-specific import…
opencli-sitemap-author
Use when creating or maintaining OpenCLI site sitemaps: agent-facing navigation, page-state, action, workflow, API-reference, pitfall, and fallback knowledge for a website. Use after browser exploration discovers durable site context, when a sitemap is stale, or when promoting local site knowledge into the repo.
interactive-login
How to complete browser/interactive logins (aws / gh / glab / gcloud). The platform backgrounds the login poller so it survives the human's browser round-trip — and when that does NOT work.
pinchtab-mcp
Use this skill when a task requires browser automation through PinchTab's MCP server connected to a remote browser instance. Covers navigation, element interaction, data extraction, form filling, multi-step flows, and session management via MCP tools.
google-safe-browsing
Prevent and fix Google Safe Browsing "Dangerous site" flags. Use when launching a public web app, buying/picking a domain, building a login or signup page, or when any site shows a red "Dangerous site" / "Deceptive site" warning in Chrome, Brave, Safari, Firefox, or Edge. Triggers on "dangerous site", "deceptive…
web-browser
Automate and interact with web pages through Chrome or Chromium using the Chrome DevTools Protocol (CDP): navigate, click, fill forms, inspect content, take screenshots, and debug console or network activity. Use when an agent needs a real browser. Prefer headless Chrome unless visible browser interaction is required.