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-securityWrote 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-security)<a href="https://agentmods.dev/skills/agent-hellboy/mcp-runtime/qa-e2e-security"><img src="https://agentmods.dev/badge/skills/agent-hellboy/mcp-runtime/qa-e2e-security/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-security"><img src="https://agentmods.dev/badge/skills/agent-hellboy/mcp-runtime/qa-e2e-security.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 6 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Data Exfiltration · line 71 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
- medium Data Exfiltration · line 114 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
- medium Data Exfiltration · line 172 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
- medium Data Exfiltration · line 175 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
- medium Data Exfiltration · line 256 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
- medium Data Exfiltration · line 262 Data is being sent to an external URL. This could be legitimate telemetry or data exfiltration. Manual review is recommended.Fix: Verify the destination URL is trusted and necessary. Remove or replace with documented APIs. Ensure no secrets, tokens, or PII are transmitted.
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.00116 | $0.04612 |
| Opus 5.5 | $0.00046 | $0.01845 |
| Sonnet 5.5 | $0.00023 | $0.00922 |
| Haiku 4.5 | $0.00012 | $0.00461 |
Grade A, and why
qa-e2e-security 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 -sS -o /dev/null -w "anon=%{http_code}\n" \ How it starts
The opening of the file, as written. The whole thing — 355 lines — stays where its author put it; the contents beside it link to each section on GitHub.
QA — E2E Security (live cluster)
Overview
security-audit and security-audit-platform are static reviews — diff,
code paths, scanner output. This skill is the dynamic counterpart: it
fires real requests at the live cluster and confirms the security
invariants actually hold at runtime. It catches policy-materialization
regressions, header middleware regressions, and audit-event regressions that
static review and unit tests miss.
Threat profiles in scope:
- anonymous → user (no key, bad key, expired session)
- user → admin (UI key vs admin key vs ingest-only key)
- agent A → agent B (grant scoping by
humanID/agentID/serverRef) - low trust → high trust tool (consent gating)
- internal pod → secret (reach API/proxy/operator secrets unprivileged)
→ for cluster RBAC/PSS coverage, defer to
k8s-hardening-audit.
Regression evidence contract: for each touched security surface, capture at least one live allow path and one live deny path, plus audit/log/header evidence where that invariant applies. Static code review can explain a finding, but it cannot close this skill as 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
Pull the three key types up front; never echo them into the report.
UI_KEY="$(kubectl get secret mcp-sentinel-secrets -n mcp-sentinel \
-o jsonpath='{.data.UI_API_KEY}' | base64 -d)"
test -n "$UI_KEY" || { echo "Failed to retrieve UI_KEY"; exit 1; }
INGEST_KEY="$(kubectl get secret mcp-sentinel-secrets -n mcp-sentinel \
-o jsonpath='{.data.INGEST_API_KEYS}' | base64 -d | cut -d, -f1)"
test -n "$INGEST_KEY" || { echo "Failed to retrieve INGEST_KEY"; exit 1; }
Step 2 — Choose mode
- head-only. Run the full backend + UI security matrix.
- git-range (
BASE=<merge-base>, defaultorigin/main). Trim by diff.
Sub-suites by changed paths:
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 · +26 lines a99e59891a6a
- 1mo ago First seen · 329 lines · 116 tokens per session scan A a9e03fa8815e
qa-e2e-security is a skill published in the GitHub repository Agent-Hellboy/mcp-runtime (6 stars, last pushed 26d ago), licensed Apache-2.0. It adds 116 tokens to every session and 4,612 once invoked, about $0.0005 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.
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.
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.
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…