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/agent-hellboy/mcp-runtime/qa-e2e-operationsnpx skills add Agent-Hellboy/mcp-runtime --skill qa-e2e-operationsgit clone --depth 1 https://github.com/Agent-Hellboy/mcp-runtimeWhat 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.00106 | $0.03168 |
| Opus 5 | $0.00053 | $0.01584 |
| Sonnet 5 | $0.00021 | $0.00634 |
| Haiku 4.5 | $0.00011 | $0.00317 |
Grade A, and why
qa-e2e-operations scanned grade A with 1 finding 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 2d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -fsS -o /dev/null -w "%{http_code}\n" http://localhost:18080/ # 200 How it starts
The opening of the file, as written. The whole thing — 297 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA — E2E Operations (live cluster)
Overview
This skill validates operations: does the operator reconcile, does the
CLI behave, does setup --test-mode produce a working stack, do rollouts
land, do CRD updates converge, does cluster doctor stay green under change?
It runs against the real Kind cluster brought up by qa-cluster-bringup,
not envtest. For code-level unit/golden/envtest checks the contributor should
run go test directly per CLAUDE.md — this skill exists to catch the
regressions those tests miss.
Regression evidence contract: every successful report must include live
cluster doctor, rollout/pod status, and the cached Kind smoke-auth,governance
traffic gate unless the diff is explicitly docs-only. If the live cluster or
traffic gate cannot run, mark the operations result blocked, not passed.
Step 1 — Confirm precondition
kubectl config current-context | grep -qx kind-mcp-runtime \
|| { echo "Run qa-cluster-bringup first"; exit 1; }
./bin/mcp-runtime cluster doctor
If cluster doctor is not green, hand back to qa-cluster-bringup rather
than firing checks at a broken cluster.
Step 2 — Choose mode
- head-only. Run the full operational matrix below.
- git-range (
BASE=<merge-base>, defaultorigin/main). Reduce the matrix to the surfaces the diff touches.
Mode dispatch by changed paths:
| Diff touches | Required sub-suites |
|---|---|
internal/operator/**, api/v1alpha1/**, config/crd/** |
Operator, CRD reconciliation, ingress, generated-file drift |
cmd/operator/**, cmd/mcp-runtime/**, internal/cli/** |
CLI smoke, generated-file drift |
internal/cli/setup/**, pkg/k8sclient/**, pkg/manifest/**, pkg/metadata/** |
Setup re-run, registry pulls, ingress, rollout |
services/platform-api/**, services/runtime-api/**, services/analytics-api/**, services/ui/**, services/ingest/**, services/processor/**, services/mcp-gateway/** |
Service rollout matrix, gateway sidecar refresh |
k8s/**, config/** |
Manifest re-apply + rollout |
docs/** only |
Skip — not an operations regression surface |
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 2d ago First seen · 297 lines · 106 tokens per session scan A 41a641b79d21
qa-e2e-operations is a skill published in the GitHub repository Agent-Hellboy/mcp-runtime (5 stars, last pushed 8d ago), licensed Apache-2.0. It adds 106 tokens to every session and 3,168 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 1 finding (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
local-frontend-check
Smoke-test or verify UI behaviour on the local Jarvis Registry frontend running at http://localhost/gateway. Use for manual regression checks, bug-fix verification, and end-to-end confirmation of specific flows without running the automated test suite.
playwright-e2e-testing
Playwright modern end-to-end testing framework with cross-browser automation, auto-wait, and built-in test runner.
webmcp-e2e
WebMCP reverse connection gateway（pairing + static/remote モード）の E2E 結合確認を実行する。Manifold 起動 → デモページ → 拡張入り Chromium → ペアリング → tools/call 検証 → タブクローズ時エラー確認までを通し、スクリーンショット証跡を残す。remote モードでは自前 JWKS + JWT で identityKey ルーティングの分離も検証する。「webmcp の E2E」「reverse gateway の動作確認」「拡張の結合テスト」で使用。.
qa-use
E2E testing and browser automation with qa-use CLI. Use when the user needs to run tests, verify features, automate browser interactions, or debug test failures.
use-agent-browser-for-airi
Test AIRI display-model imports with agent-browser across stage-tamagotchi Electron, stage-web, and stage-pocket mobile web layouts. Use when uploading and verifying contributor-supplied Live2D ZIP, VRM, or MMD ZIP/PMX/PMD files through AIRI's model selector, including onboarding bypass, format-specific import…
test-conversion
Workflow for converting unit tests to browser tests for Project Bedrock. Invoke this when the user wants to remove complex Browser dependencies from tests.