Borrowing it
Nothing to install: this file belongs to receptron/mulmoclaude. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/receptron/mulmoclaude/main/.claude/skills/e2e-live-docker/SKILL.mdgit clone --depth 1 https://github.com/receptron/mulmoclaudeWrote 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/receptron/mulmoclaude/e2e-live-docker)<a href="https://agentmods.dev/skills/receptron/mulmoclaude/e2e-live-docker"><img src="https://agentmods.dev/badge/skills/receptron/mulmoclaude/e2e-live-docker/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/receptron/mulmoclaude/e2e-live-docker"><img src="https://agentmods.dev/badge/skills/receptron/mulmoclaude/e2e-live-docker.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, 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 MCP Rug Pull · line 37 npx commands without a version suffix (e.g. @1.0.0) create a rug-pull risk if the upstream server is compromised and publishes a malicious update.Fix: Pin the version: npx @scope/[email protected]
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.00085 | $0.01001 |
| Opus 5 | $0.00043 | $0.00500 |
| Sonnet 5 | $0.00017 | $0.00200 |
| Haiku 4.5 | $0.00009 | $0.00100 |
Grade A, and why
e2e-live-docker scanned grade A with 0 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 10d 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
前提
yarn devを別ターミナルで起動済み(http://localhost:5173が応答する)DISABLE_SANDBOXを unset で起動していること。/api/sandboxの payload は enabled 時{ sshAgent, mounts }、 disabled 時 空オブジェクト{}を返す(server/api/sandboxStatus.ts参照)。spec 側のgetSandboxStatus(page)helper はこの{}をnullに正規化するので、 sandbox off だと spec の gate がnull === nullで hit して全 test がtest.skipで抜ける- Docker daemon が起動しており、
mulmoclaude-sandboximage が build 済(yarn dev初回起動時に自動 build) - Claude 認証済み(
claude login済み orANTHROPIC_API_KEY設定済み) - 各シナリオ固有の前提(unmet なら spec が
test.skipで抜ける、 ログにスキップ理由が出る):- L-23:
X_BEARER_TOKENが host の env に設定されていること - L-28:
SANDBOX_MOUNT_CONFIGS=ghまたはSANDBOX_SSH_AGENT_FORWARD=1のいずれかが設定されていること
- L-23:
実行
yarn test:e2e:live:docker
デバッグ時
HEADED=1 yarn test:e2e:live:docker
カバーするシナリオ
- L-23: X MCP tools (
readXPost/searchX) が Docker サンドボックス on 状態で host のX_BEARER_TOKENを見て enabled になる(B-01 回帰) - L-26: サンドボックス on 状態で開始したセッションが reload で「No conversation found」 を出さず履歴復元される(B-04 回帰、 in-container workspace path 整合)
- L-28: agent が container 内で
gh auth statusを Bash 実行し、 host の gh credential が container に届いていることを確認する(B-06 回帰)
結果の確認
- 詳細:
playwright-report-live/docker/index.html(このカテゴリ専用サブディレクトリに出力されるので、 親/e2e-liveの総合レポートは上書きされない) - 動画リプレイ:
npx playwright show-trace test-results-live/docker/<spec>/trace.zip
fake-echo / CI matrix について
このカテゴリは fake-echo backend (MULMOCLAUDE_FAKE_AGENT=1) で再現できない(実 Docker サンドボックス起動が必要)ので、 .github/workflows/e2e_live_no_llm.yaml の matrix には 意図的に登録していない。 同等の理由で各 test も E2E_LIVE_NO_LLM=1 が立っていると skip する。 routine な CI 検証ではなく 開発者が手元で Docker on モードを切り替えて回す ことを想定したスイート。
Docker on/off の検証も必要な場合
このカテゴリは Docker on 必須で、 off では全 test が test.skip するだけ。 「両モード巡回」 を取りたい時は 1) 現在モード (/api/sandbox の payload で確認) で yarn test:e2e:live:docker を回す、 2) もう一方のモードに dev を再起動して yarn test:e2e:live を回して他カテゴリの両モード健全性を見る、 の併用が想定。
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.
- 10d ago First seen · 46 lines · 85 tokens per session scan A 0ea92ca1f034
e2e-live-docker is a skill published in the GitHub repository receptron/mulmoclaude (346 stars, last pushed yesterday), licensed MIT. It adds 85 tokens to every session and 1,001 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
verify
Build the computer-use-demo image and drive the Streamlit UI headlessly to verify changes end-to-end.
zero-script-qa
Zero Script QA — test without scripts using structured JSON logging and Docker monitoring. Triggers: zero-script-qa, log testing, docker logs, QA.
local-test
Build, run, and test IronClaw locally using Docker containers and Chrome MCP browser automation.
branchbox-devcontainer-guardrails
Use when modifying BranchBox devcontainer/bootstrap workflows, compose templates, feature env-stash behavior, or manual E2E harness/release docs. Apply issue.
local-controller-testing-workflow-github
Use when you need to run MintMaker controller code locally against a real Kubernetes cluster (minikube or kind) with repo hosted on GitHub, create test Component/DependencyUpdateCheck resources, and iterate quickly across macOS and Linux.
blackbox-testing
Automates end-to-end and system validation tests. Runs services via Docker, feeds inputs, executes scenarios, and verifies outputs.