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/bun913/mcp-testrail/e2e-setupnpx skills add bun913/mcp-testrail --skill e2e-setupgit clone --depth 1 https://github.com/bun913/mcp-testrailWrote 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/bun913/mcp-testrail/e2e-setup)<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>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.00040 | $0.01793 |
| Opus 5 | $0.00020 | $0.00897 |
| Sonnet 5 | $0.00008 | $0.00359 |
| Haiku 4.5 | $0.00004 | $0.00179 |
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:*) Copies of this mod
1 near-identical copy found in the catalogue:
- e2e-setup — 100% identical, 0 lines differ
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/cliis indevDependenciesand available asnpm run playwright-cli- Chromium must be installed:
npx playwright install chromiumif 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>
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 · 211 lines · 40 tokens per session scan B b30cc07c952f
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.
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.
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.
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.
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…