Borrowing it
Nothing to install: this file belongs to akiojin/llmlb. 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/akiojin/llmlb/develop/.claude/commands/e2e.dashboard.mdgit clone --depth 1 https://github.com/akiojin/llmlbWrote 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/commands/akiojin/llmlb/e2e.dashboard)<a href="https://agentmods.dev/commands/akiojin/llmlb/e2e.dashboard"><img src="https://agentmods.dev/badge/commands/akiojin/llmlb/e2e.dashboard/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/commands/akiojin/llmlb/e2e.dashboard"><img src="https://agentmods.dev/badge/commands/akiojin/llmlb/e2e.dashboard.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00019 | $0.01318 |
| Opus 5.5 | $0.00008 | $0.00527 |
| Sonnet 5.5 | $0.00004 | $0.00264 |
| Haiku 4.5 | $0.00002 | $0.00132 |
Grade A, and why
e2e.dashboard 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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Input
$ARGUMENTS
You MUST consider the user input before proceeding (if not empty).
Goal
MCP Playwrightツールを使用して、LLM Router DashboardのE2Eテストを対話的に実行する。 ブラウザを起動し、各UI要素の動作を検証し、スクリーンショットで結果を記録する。
Prerequisites
- llmlbサーバーが
http://localhost:8080で起動していること - サーバーが起動していない場合は、別ターミナルで
cargo run --release -p llmlbを実行
Test Scenarios
Phase 1: 初期表示テスト
- ナビゲーション:
/dashboardにアクセス - 初期スクリーンショット: 初期状態を記録
- 要素存在確認:
- ヘッダー (
header.page-header) - Stats Grid (
.stats-grid) - Models Section (
#tab-models) - Nodes Table (
#nodes-body)
- ヘッダー (
Phase 2: Header Controls テスト
| ID | テスト内容 | セレクタ | 操作 |
|---|---|---|---|
| H-01 | テーマ切替 | #theme-toggle |
3回クリック (minimal→tech→creative→minimal) |
| H-02 | Playgroundボタン | #chat-open |
クリック→モーダル表示確認→閉じる |
| H-03 | API Keysボタン | #api-keys-button |
クリック→モーダル表示確認→閉じる |
| H-04 | Refreshボタン | #refresh-button |
クリック→ステータス更新確認 |
| H-05 | 接続ステータス | #connection-status |
テキスト確認 |
Phase 3: Stats Grid テスト
| ID | テスト内容 | セレクタ |
|---|---|---|
| S-01 | Total Nodes | [data-stat="total-nodes"] |
| S-02 | Online Nodes | [data-stat="online-nodes"] |
| S-03 | Offline Nodes | [data-stat="offline-nodes"] |
| S-04 | Total Requests | [data-stat="total-requests"] |
| S-05 | GPU Usage | [data-stat="average-gpu-usage"] |
Phase 4: Models Tab テスト
| ID | テスト内容 | セレクタ | 操作 |
|---|---|---|---|
| M-01 | Localタブ | button[role="tab"]:has-text("Local") |
存在確認・クリック |
| M-02 | Model Hubタブ | button[role="tab"]:has-text("Model Hub") |
存在確認・クリック |
| M-03 | ローカルモデル一覧 | #local-models-list |
内容確認 |
| M-04 | Model Hubカード | [data-testid="model-card"] |
内容確認 |
| M-05 | Pullボタン | button:has-text("Pull") |
存在確認・クリック |
Phase 5: Nodes Tab テスト
| ID | テスト内容 | セレクタ | 操作 |
|---|---|---|---|
| N-01 | ノード一覧 | #nodes-body |
行数確認 |
| N-02 | ステータスフィルタ | #filter-status |
各オプション選択 |
| N-03 | 検索フィルタ | #filter-query |
テキスト入力 |
| N-04 | Export JSON | #export-json |
クリック |
| N-05 | Export CSV | #export-csv |
クリック |
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.
- 8d ago First seen · 130 lines · 19 tokens per session scan A 406d8ead0855
e2e.dashboard is a command published in the GitHub repository akiojin/llmlb (10 stars, last pushed 2d ago), licensed MIT. It adds 19 tokens to every session and 1,318 once invoked, about $0.0001 per session on Opus 5.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-10-21.
Other commands, from other repositories
expect
Diff-aware AI browser testing — reads the git diff, maps changes to affected pages via the route map, generates a targeted test plan, and executes it via agent-browser (Rust daemon + CDP, ARIA-tree-first) with pass/fail reporting. Use when testing UI changes, verifying PRs before merge, or running regression checks on…
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
amazing-e2e-check
Run explicitly requested E2E, browser, device, or installed-deployment scenarios in an independent verification workflow.
record
Record a browser walkthrough of a URL using Antigravity (agy). Generates .webm video, screenshots, and a report. Auto-converts to MP4 if ffmpeg is available.
verify-pr
Verify a PR's frontend changes through browser automation.
auto-verify
A command for checking a website's front-end user experience with Playwright, a tool that automates web browsers.