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/sabbour/agentweaver/ui-harnessnpx skills add sabbour/agentweaver --skill ui-harnessgit clone --depth 1 https://github.com/sabbour/agentweaverWrote 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/sabbour/agentweaver/ui-harness)<a href="https://agentmods.dev/skills/sabbour/agentweaver/ui-harness"><img src="https://agentmods.dev/badge/skills/sabbour/agentweaver/ui-harness.svg" alt="Measured on agentmods" 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 | $0.00043 | $0.01949 |
| Opus 5 | $0.00022 | $0.00975 |
| Sonnet 5 | $0.00009 | $0.00390 |
| Haiku 4.5 | $0.00004 | $0.00195 |
Grade A, and why
ui-harness-cli 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 today.
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 — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
UI harness CLI contract
Use this harness to capture deterministic browser evidence for a persona against an
Agentweaver deployment. It is a driver, not a UX judge: finish emits driver P0 facts
and normalized evidence for scripts/harness-judge/; do not call subjective UX quality
verified solely from its output.
Prerequisites
From the repository root, install the harness dependencies and run its fixture tests:
node scripts/ci/shared-deps.mjs ensure --project scripts/ui-harness
npm --prefix scripts/ui-harness test
Targets are host-agnostic. Require an absolute HTTPS URL except for loopback HTTP, keep normal TLS validation enabled, and reject URL credentials/fragments. Automated browser requests and navigation stay on the configured app origin; only the explicit headful login flow may visit configured identity-provider origins.
Authentication
Agentweaver staging uses Microsoft Entra Conditional Access, which blocks plain Chromium (and device-code flow). Authentication must use the managed Edge Default profile on Windows (enrolled device).
Option A — Edge is not currently running (preferred)
Close all Edge windows first (save any open work — they will be lost), then:
node scripts/ui-harness/login-edge-default.mjs --base-url https://<host>.staging.<domain>
This launches the real Edge Default profile (%LOCALAPPDATA%\Microsoft\Edge\User Data).
Entra SSO often completes automatically. If the sign-in page appears, complete it in the
Edge window, then press Resume in the Playwright Inspector.
Option B — Edge is already running (CDP attach)
Relaunch Edge with remote debugging (requires closing the current Edge first):
Start-Process msedge.exe "--remote-debugging-port=9222 --user-data-dir=`"$env:LOCALAPPDATA\Microsoft\Edge\User Data`" --profile-directory=Default --no-first-run https://<host>.staging.<domain>"
Then connect and capture:
node scripts/ui-harness/login-edge-default.mjs --base-url https://<host>.staging.<domain> --cdp
What ships with it
32 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.
- .gitignore 94 B
- agent-driver-ui/session-worker.mjs 12 KB runs code
- agent-driver-ui/tools.mjs 13 KB runs code
- lib/auth.mjs 3.9 KB runs code
- lib/browser.mjs 6.6 KB runs code
- lib/crossref.mjs 506 B runs code
- lib/drag.mjs 3.5 KB runs code
- lib/evidence.mjs 2.7 KB runs code
- lib/readiness.mjs 3.4 KB runs code
- lib/reporter-ui.mjs 2.4 KB runs code
- lib/session-runtime.mjs 17 KB runs code
- lib/session-store.mjs 1.2 KB runs code
- lib/ui-actions.mjs 4.5 KB runs code
- login-capture-edge.mjs 2.3 KB runs code
- login-edge-default.mjs 8.2 KB runs code
- package-lock.json 2.3 KB
- package.json 459 B
- playwright.config.ts 199 B runs code
- README.md 3.7 KB
- test/auth.test.mjs 3.9 KB runs code
- test/browser.test.mjs 10 KB runs code
- test/drag.test.mjs 3.5 KB runs code
- test/evidence.test.mjs 1.3 KB runs code
- test/fixtures/app-shell-dom.json 256 B
- test/fixtures/auth-loading-dom.json 137 B
- test/fixtures/session-worker-close-failure.mjs 1.0 KB runs code
- test/fixtures/sign-in-dom.json 140 B
- test/init.test.mjs 461 B runs code
- test/multi-process-session.test.mjs 20 KB runs code
- test/readiness.test.mjs 4.4 KB runs code
- test/reporter-ui.test.mjs 12 KB runs code
- test/ui-adapter.test.mjs 3.2 KB runs code
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.
- today Changed · +2 lines 911630ff0046
- yesterday First seen · 167 lines · 43 tokens per session scan A f1d19393a2cc
ui-harness-cli is a skill published in the GitHub repository sabbour/agentweaver (5 stars, last pushed today), licensed MIT. It adds 43 tokens to every session and 1,949 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
webapp-testing
Start/reuse a local app, wait for readiness, inspect rendered state/console/network, act from observed selectors, and verify with evidence.
tutti-record-agent-session-replay
From a Tutti checkout, run, audit, freshly replay, publish, or diagnose Session Replay cassettes that are driven by case-repository scenario scripts (CDP), not by interactive UI recording. Use for real-Provider capture while a scenario.mjs executes, cassette transport or semantic-state mismatches, fresh replay…
qa
Browser-based QA verification. Launches a real browser, navigates the app, clicks buttons, fills forms, and tests user flows. Works as a standalone skill or as a phase end condition in campaigns. Requires Playwright (optional dependency, graceful skip if not installed).
playwright-visual-testing
Add, repair, or review Playwright visual regression tests for browser-facing .NET apps, including screenshot baselines, Pixelmatch thresholds, deterministic rendering, and GitHub Actions artifacts. USE FOR: toHaveScreenshot, page.screenshot visual checks, Pixelmatch/pngjs comparison scripts, visual baseline updates…
Ark Dashboard and UI Testing
Test the Ark Dashboard and UI with Playwright and create PRs with screenshots. Use this skill when testing dashboard UI, taking screenshots for PRs, or validating dashboard changes.
chrome-automation
Chrome 浏览器自动化操作。当用户需要自动化浏览器操作、网页测试、数据抓取或 UI 自动化时使用此技能。.