PlayWright-MCP-Repo: Skill for Claude Code

.claude/skills/e2e-setup/SKILL.md

e2e-setup is a skill for Claude Code from valvacchs/PlayWright-MCP-Repo. It costs 40 tokens per session (1,793 once invoked), scanned B, a copy of e2e-setup, MIT.

A setup workflow for creating and checking TestRail demo-site API credentials, then updating the project’s MCP configuration file.

In plain words
What is it for?
It checks existing credentials, removes stale keys, creates a new key through Playwright, verifies access, and updates .mcp.json.
Why use it?
It removes the manual steps of finding valid credentials and making TestRail tools available to the current coding-agent session.

Skill for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: mentions Claude Code.

This is valvacchs/PlayWright-MCP-Repo's own configuration. It tells Claude Code how to work on PlayWright-MCP-Repo itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything PlayWright-MCP-Repo configures →

Reuse

Borrowing it

Nothing to install: this file belongs to valvacchs/PlayWright-MCP-Repo. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/valvacchs/PlayWright-MCP-Repo/main/.claude/skills/e2e-setup/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/valvacchs/PlayWright-MCP-Repo

Made for: Claude Code.

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.

agentmods badge for e2e-setup

README.md
[![agentmods](https://agentmods.dev/badge/skills/valvacchs/playwright-mcp-repo/e2e-setup/github.svg)](https://agentmods.dev/skills/valvacchs/playwright-mcp-repo/e2e-setup)
Your own site
<a href="https://agentmods.dev/skills/valvacchs/playwright-mcp-repo/e2e-setup"><img src="https://agentmods.dev/badge/skills/valvacchs/playwright-mcp-repo/e2e-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.

agentmods 80×15 button for e2e-setup

Your own site · 80×15
<a href="https://agentmods.dev/skills/valvacchs/playwright-mcp-repo/e2e-setup"><img src="https://agentmods.dev/badge/skills/valvacchs/playwright-mcp-repo/e2e-setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 40 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,793 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 2 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin 100% copy Near-identical to another mod 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00040 $0.01793
Opus 5 $0.00020 $0.00897
Sonnet 5 $0.00008 $0.00359
Haiku 4.5 $0.00004 $0.00179

Measured 9d ago against content hash b30cc07c952f, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade B, and why

e2e-setup scanned grade B 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 9d 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.

Reads MCP configurationmediumAgent snooping

mcp.json carries server URLs and auth tokens; reading it lets a mod discover and abuse other integrations.

test -f .mcp.json && cat .mcp.json

Makes network callslowCapability

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

allowed-tools: Bash(npm run playwright-cli:*), Bash(curl:*), Bash(npm:*), Bash(node:*), Bash(date:*), Bash(test:*)
Origin

This is a copy

100% identical to e2e-setup — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.

.claude/skills/e2e-setup/SKILL.md · 211 lines

How it starts

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

TestRail E2E Setup

Overview

Ensures .mcp.json is configured with valid TestRail credentials so that mcp__testrail__* tools are available in the current Claude Code session.

Output: A valid .mcp.json file that Claude Code recognizes as MCP server config.

Prerequisites

  • @playwright/cli is in devDependencies and available as npm run playwright-cli
  • Chromium must be installed: npx playwright install chromium if needed

Step 1: Check if .mcp.json already works

test -f .mcp.json && cat .mcp.json

If .mcp.json exists, verify the credentials work:

TESTRAIL_URL=$(node -e "const c=JSON.parse(require('fs').readFileSync('.mcp.json','utf8'));console.log(c.mcpServers.testrail.env.TESTRAIL_URL)")
TESTRAIL_USERNAME=$(node -e "const c=JSON.parse(require('fs').readFileSync('.mcp.json','utf8'));console.log(c.mcpServers.testrail.env.TESTRAIL_USERNAME)")
TESTRAIL_API_KEY=$(node -e "const c=JSON.parse(require('fs').readFileSync('.mcp.json','utf8'));console.log(c.mcpServers.testrail.env.TESTRAIL_API_KEY)")
curl -s -w "\nHTTP_STATUS:%{http_code}" \
  -u "$TESTRAIL_USERNAME:$TESTRAIL_API_KEY" \
  "${TESTRAIL_URL}/index.php?/api/v2/get_projects"
  • HTTP 200 -> setup complete, skip to Step 6
  • HTTP 401 or file missing -> continue to Step 2

Step 2: Get latest credentials

Use WebFetch on this URL to extract login ID, password, and demo URL:

https://www.techmatrix.co.jp/product/testrail/demo_site.html

Step 3: Login to TestRail via playwright-cli

All playwright-cli commands are run via npm run playwright-cli --.

3a. Open login page

npm run playwright-cli -- open '<DEMO_SITE_URL>/index.php?/auth/login'
npm run playwright-cli -- snapshot

3b. Fill login form and submit

Known selectors (as of 2026-03):

  • Email: input[name="name"]
  • Password: input[name="password"]
  • Submit: #button_primary

Use snapshot refs to fill and click:

npm run playwright-cli -- fill <email_ref> "<LOGIN_ID>"
npm run playwright-cli -- fill <password_ref> "<PASSWORD>"
npm run playwright-cli -- click <login_button_ref>

Read the full file on GitHub · 211 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.

  1. 9d ago First seen · 211 lines · 40 tokens per session scan B b30cc07c952f

Subscribe to this mod's changes

e2e-setup is a skill published in the GitHub repository valvacchs/PlayWright-MCP-Repo (0 stars, last pushed 2mo ago), licensed MIT. It adds 40 tokens to every session and 1,793 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 2 findings (reads mcp configuration, makes network calls). It is 100% identical to e2e-setup, differing in 0 lines, and is treated as a copy.

Related

Other skills, from other repositories

systematic-debugging

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

obra/superpowers · 21 tokens

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

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens