Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/Agent-Hellboy/mcp-runtimenpx agentmods add skills/agent-hellboy/mcp-runtime/qa-e2e-operationsWrote 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/agent-hellboy/mcp-runtime/qa-e2e-operations)<a href="https://agentmods.dev/skills/agent-hellboy/mcp-runtime/qa-e2e-operations"><img src="https://agentmods.dev/badge/skills/agent-hellboy/mcp-runtime/qa-e2e-operations/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.
<a href="https://agentmods.dev/skills/agent-hellboy/mcp-runtime/qa-e2e-operations"><img src="https://agentmods.dev/badge/skills/agent-hellboy/mcp-runtime/qa-e2e-operations.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.1 | $0.00106 | $0.03183 |
| Opus 5.5 | $0.00042 | $0.01273 |
| Sonnet 5.5 | $0.00021 | $0.00637 |
| Haiku 4.5 | $0.00011 | $0.00318 |
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 1mo 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.
- 1mo ago Changed 9dc2c51b79af
- 1mo 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 (6 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 106 tokens to every session and 3,183 once invoked, about $0.0004 per session on Opus 5.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
generate-e2e-tests
Walk a flow in the browser and write end-to-end tests (Playwright, Cypress, etc.) that reproduce it. Use when asked to create e2e coverage for a user flow.
smoke-test
Smoke-test a user flow end to end in a browser (login, checkout, signup, etc.) and verify the expected result. Use when asked to walk through a flow and confirm it still works.
run-mcpjam-evals
Drive MCPJam's hosted eval tools end to end — check what a run will cost and disclose, launch it, poll it to a verdict, and triage a failure down to the step that failed. Use when connected to MCPJam's MCP server and asked to run, re-run, investigate, or compare eval results, rather than to author eval files locally.
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.
verify-omnigent
Drive Omnigent the way a user does and prove a behavior with recorded evidence, using an isolated server, runner, and mock model plus a feature map of every user entry point. Load before reproducing a user-facing bug, before claiming a fix works, or when reviewing whether a change covered every surface (session vs.…
test-master
Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation…