A one-time setup procedure for running the uat-agents testing tools in WSL2, which is Linux running inside Windows. It checks Node.js, configures Chrome control, and copies a helper script into the project.

Use it once per project to check the environment, add the Chrome DevTools MCP configuration, install the helper, and follow the remaining Windows instructions.

It prepares a project for browser tests without requiring the user to perform every configuration step manually.

setup — Skill for Claude Code by theelims/license-to-code

Install

Getting it into your agent

This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.

Claude Code

/plugin marketplace add theelims/license-to-code

Claude Code

/plugin install uat-agents

Made for: Claude Code.

Or install uat-agents, the plugin that ships this one along with the rest of its 2 skills, 1 agent.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/theelims/license-to-code/setup/github.svg)](https://agentmods.dev/skills/theelims/license-to-code/setup)

Your own site

<a href="https://agentmods.dev/skills/theelims/license-to-code/setup"><img src="https://agentmods.dev/badge/skills/theelims/license-to-code/setup/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/theelims/license-to-code/setup"><img src="https://agentmods.dev/badge/skills/theelims/license-to-code/setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 71 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,376 The whole file, excluding the scripts and references it only reads on demand.

Security scan C 2 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

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.00071	$0.01376
Opus 5.5	$0.00028	$0.00550
Sonnet 5.5	$0.00014	$0.00275
Haiku 4.5	$0.00007	$0.00138

Measured 1mo ago against content hash 8d42f46ae235, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade C, and why

setup scanned grade C with 2 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.

Downloads and executes remote codehighSupply chain

curl | sh runs whatever the server returns today, which is not necessarily what it returned when this was reviewed.

> curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.40.3/install.sh | bash

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

> curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.40.3/install.sh | bash

plugins/uat-agents/skills/setup/SKILL.md · 165 lines

How it starts

The opening of the file, as written. The whole thing — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.

UAT Agents Setup Skill

You are the setup agent for the uat-agents plugin. Your job is to configure this project so /uat-agents:test can control Chrome via the chrome-devtools MCP server.

You perform all automated steps yourself and give the user exact, copy-paste-ready instructions for the steps that require Windows access.

Hard rules

WSL-only. This skill is designed for WSL2. Stop with a clear message if not in WSL.
Idempotent. Running this skill twice must leave the project in the same state as running it once.
No changes outside the project root. Do not modify ~/.claude/, global settings, or files outside the directory where the user invoked this skill.
Fail loudly on missing Node. If Node is absent or too old, give the exact install command and stop. Do not write config files for an MCP server that cannot launch.

Workflow

Step 1 — Verify WSL2 environment

Run: grep -qi microsoft /proc/version && echo yes || echo no

If the output is no, stop:

This setup skill is for WSL2 only. On native Linux or macOS, write .mcp.json directly and launch Chrome with --remote-debugging-port=9222 yourself.

Step 2 — Check Node.js version

Run: node --version 2>/dev/null || echo MISSING

Parse the major version number.

MISSING: Tell the user:
Node.js is not installed. chrome-devtools-mcp requires Node ≥20.19. Install via nvm (recommended for WSL):
```
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.40.3/install.sh | bash
# Close and reopen your terminal, then:
nvm install --lts
```
Re-run /uat-agents:setup once Node is installed.
Then stop.
Version < 20: Tell the user:
Node.js {version} is too old. chrome-devtools-mcp requires Node ≥20.19. Upgrade:
```
nvm install --lts && nvm use --lts
```
Re-run /uat-agents:setup once Node is upgraded.
Then stop.
Version ≥ 20: Continue.

Step 3 — Write .mcp.json

Read the full file on GitHub · 165 lines

Changes

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 · 165 lines · 71 tokens per session scan C 8d42f46ae235

Subscribe to this mod's changes

setup is a skill published in the GitHub repository theelims/license-to-code (2 stars, last pushed 5mo ago), licensed MIT. It adds 71 tokens to every session and 1,376 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it C with 2 findings (downloads and executes remote code, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

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…

microsoft/ai-agents-for-beginners · 200 tokens

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…

vercel/next.js · 95 tokens

chronicle

Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…

microsoft/vscode · 72 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

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.

microsoft/vscode · 53 tokens

component-fixtures

Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.