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/it235/multica-best-practicesnpx agentmods add skills/it235/multica-best-practices/multica-test-t3-ui-automationWrote 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/it235/multica-best-practices/multica-test-t3-ui-automation)<a href="https://agentmods.dev/skills/it235/multica-best-practices/multica-test-t3-ui-automation"><img src="https://agentmods.dev/badge/skills/it235/multica-best-practices/multica-test-t3-ui-automation/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/it235/multica-best-practices/multica-test-t3-ui-automation"><img src="https://agentmods.dev/badge/skills/it235/multica-best-practices/multica-test-t3-ui-automation.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.00056 | $0.00581 |
| Opus 5.5 | $0.00022 | $0.00232 |
| Sonnet 5.5 | $0.00011 | $0.00116 |
| Haiku 4.5 | $0.00006 | $0.00058 |
Grade A, and why
multica-test-t3-ui-automation 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 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.
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
UI Automation (T3 · UI)
T3 only after G2.5 PASS; an AC can only be verified by UI → run this skill alone; if it also has an API channel → run both, orchestration merges one report.
Integrated from
ui-automation-squad. Material assembly + BLOCKED seemultica-test-orchestration.
Required Items (stop + interruption list if missing; summary from comments)
| Required | How it counts as complete |
|---|---|
| G2.5 PASS | Leader/DevOps explicit G2.5 PASS (or deploy_url + Leader written authorization) |
| deploy_url | Reachable environment URL |
| page_url | Page URL; if omitted must equal deploy_url (state in comments) |
| e2e script | Path in MULTICA.md §2; in deploy branch at G2.5 SHA, 1:1 with cases |
| ui_auth | auth_mode=none or "account via Secret variable name"; never plaintext password from comments |
Never use xmind-ui-automation / playwright.git / req-figma-ui-automation as prerequisites.
Flow
pytest <MULTICA.md §2 e2e path> --base-url <page_url> --alluredir ./reports/ui
Cases source: T1 Confluence t1-cases + T2 supplement. Missing script path → interruption list.
Output and merge
# T3 UI Automation — {JIRA_KEY}
- G2.5: PASS @ {sha} deploy: {url} page: {page_url}
- e2e: {MULTICA.md §2 path}
- total / pass / fail / error
- per case: id / title / status / screenshot / log path
- conclusion: PASS | FAIL | BLOCKED
multica-test-orchestration merges with API side: one side only verifies a given AC, missing that side → whole ticket cannot be PASS; errors → triage (references/t3-failure-triage.md).
Why it works
UI verification bound to the actual deployed page; 1:1 with cases avoids "runs but doesn't cover"; running after G2.5 avoids a green build masking a broken environment.
What ships with it
2 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 · -56 lines · +5 tokens per session b9f088f29785
- 1mo ago First seen · 108 lines · 51 tokens per session scan A 5687b6105599
multica-test-t3-ui-automation is a skill published in the GitHub repository it235/multica-best-practices (212 stars, last pushed 1mo ago), licensed MIT. It adds 56 tokens to every session and 581 once invoked, about $0.0002 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-09-07.
Other skills, from other repositories
browse
Drive a real browser through Aside: open a page, read it, click through a flow, take screenshots, check console errors. (gstack).
cua-driver
Use Cua Driver for desktop or browser tasks that are awkward or unavailable through Bash/APIs, or when the user explicitly wants GUI interaction: app testing, visual bug reproduction, form filling, calendar entry, screenshots, and demo recording. Also covers Cua setup; not OpenAI Codex Computer Use or web research.
create-verification-skill
Create a repo-local verification skill and exhaustive feature map for driving a real app through its UI, CLI, or API. Use for "create a verification skill", "make a verify skill for this repo", or "document how agents can verify this app".
browser-qa
A browser-based quality check for deployed web pages and user flows. It uses browser automation to test rendering, navigation, forms, interactions, responsive behaviour, and accessibility-related issues.
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.
test-electron-app
Drive the real running PostHog Electron app (live tRPC, workspace-server, real data) over CDP with agent-browser. Connect to the running app on port 9222, test desktop changes against a local Django stack, snapshot the accessibility tree, inspect network requests, and screenshot only when explicitly asked. Use when…