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/theelims/license-to-code/setupnpx skills add theelims/license-to-code --skill setupgit clone --depth 1 https://github.com/theelims/license-to-codeWhat 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.00071 | $0.01376 |
| Opus 5 | $0.00036 | $0.00688 |
| Sonnet 5 | $0.00014 | $0.00275 |
| Haiku 4.5 | $0.00007 | $0.00138 |
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 yesterday.
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 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.jsondirectly and launch Chrome with--remote-debugging-port=9222yourself.
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-mcprequires Node ≥20.19. Install vianvm(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 --ltsRe-run
/uat-agents:setuponce Node is installed.Then stop.
-
Version < 20: Tell the user:
Node.js
{version}is too old.chrome-devtools-mcprequires Node ≥20.19. Upgrade:nvm install --lts && nvm use --ltsRe-run
/uat-agents:setuponce Node is upgraded.Then stop.
-
Version ≥ 20: Continue.
Step 3 — Write .mcp.json
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.
- yesterday First seen · 165 lines · 71 tokens per session scan C 8d42f46ae235
setup is a skill published in the GitHub repository theelims/license-to-code (2 stars, last pushed 4mo ago), licensed MIT. It adds 71 tokens to every session and 1,376 once invoked, about $0.0004 per session on Opus 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.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
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.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…