e2e-setup

e2e-setup is a skill for Claude Code, Codex from bun913/mcp-testrail. It costs 40 tokens per session (1,793 once invoked), scanned B, original, MIT.

A setup skill that creates and verifies API access for a TestRail demo site. TestRail is a web service for organizing test cases, test runs, and results; an API key is a secret used to access it programmatically.

In plain words
What is it for?
For checking existing TestRail access, deleting keys at least 72 hours old, generating a new key with Playwright, verifying access, and updating the project’s MCP configuration.
Why use it?
It removes the manual work of checking credentials, replacing old keys, and configuring the MCP server. It updates .mcp.json so the TestRail tools can be used in the current coding session.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/bun913/mcp-testrail/e2e-setup
Any agent
npx skills add bun913/mcp-testrail --skill e2e-setup
Clone the repo
git clone --depth 1 https://github.com/bun913/mcp-testrail

Made for: Claude Code, Codex.

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/bun913/mcp-testrail/e2e-setup.svg)](https://agentmods.dev/skills/bun913/mcp-testrail/e2e-setup)
Your own site
<a href="https://agentmods.dev/skills/bun913/mcp-testrail/e2e-setup"><img src="https://agentmods.dev/badge/skills/bun913/mcp-testrail/e2e-setup.svg" alt="Measured on agentmods" 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. Scan, not verified.
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.

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

Measured 4d ago against content hash b30cc07c952f, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, 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 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.

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

Copies of this mod

1 near-identical copy found in the catalogue:

  • e2e-setup — 100% identical, 0 lines differ
.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. 4d 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 bun913/mcp-testrail (44 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). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

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

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.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 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

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…

microsoft/vscode · 71 tokens