Getting it into your agent
There is no command for this one: it runs only inside a plugin, and the catalogue could not identify which plugin ships it. The source is linked below.
Wrote 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/onedro1d/dark-factory/df-ui-verify)<a href="https://agentmods.dev/skills/onedro1d/dark-factory/df-ui-verify"><img src="https://agentmods.dev/badge/skills/onedro1d/dark-factory/df-ui-verify/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/onedro1d/dark-factory/df-ui-verify"><img src="https://agentmods.dev/badge/skills/onedro1d/dark-factory/df-ui-verify.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.00085 | $0.02149 |
| Opus 5 | $0.00043 | $0.01074 |
| Sonnet 5 | $0.00017 | $0.00430 |
| Haiku 4.5 | $0.00009 | $0.00215 |
Grade A, and why
df-ui-verify 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 9d 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Dark Factory — Authed UI Verification (df-ui-verify)
Overview
df-ui-verify drives and verifies a Clerk-protected web UI end-to-end with no human login. It is a feeder to df-qa: the mechanism by which QA gets "eyes on" an authed front-end. Two phases (the df convention): a deterministic auth script mints a real Clerk session and writes a Playwright storageState; then the agent drives the live UI per PO scenarios, capturing browser-surface evidence and a verdict.
The auth breakthrough that makes this universal: the backend dev_browser handshake mints the __clerk_db_jwt that the old "headed-login → capture storageState" flow could only get from a real browser. With it, the whole flow runs headless from a backend secret key.
Scope — the kernel, not your drivers
This skill ships the portable half: session minting, storageState assembly, evidence layout, and the verdict rule. It ships no application drivers. The per-app click-through scripts — the ones that know your routes, your selectors and your host — belong in the layer that owns the app, not in a generic method repo. Keep them beside the app or in your org's layer, and treat this skill as what they call.
When to use
- Verifying a deployed, Clerk-gated UI against PO requirements / test scenarios.
- "Look at the website and click through it" — agent-driven exploratory verification.
- Capturing per-scenario UI evidence for a df-qa verdict.
Phase 1 — Authenticate (run the script)
Populate skills/df-ui-verify/.env.local (gitignored), then run the kernel:
bash "${CLAUDE_PLUGIN_ROOT:-$HOME/.claude/skills/df-ui-verify}/scripts/clerk-auth.sh"
Env contract:
| Var | Meaning |
|---|---|
CLERK_SECRET_KEY |
sk_test_* (dev). Drives instance detection. Never logged beyond its prefix. |
CLERK_FRONTEND_API |
Frontend API host, e.g. https://<slug>.clerk.accounts.dev. |
CLERK_USER_ID |
user_… to impersonate. (Or set CLERK_USER_EMAIL and the script resolves it.) |
APP_ORIGIN |
App origin — must be in Clerk Allowed Origins. Sent as Origin header. |
APP_BASE_URL |
Where the UI is served (navigate target). |
What ships with it
11 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.
- scripts/clerk-auth.sh 4.8 KB runs code
- scripts/inject-session.template.js 1.2 KB runs code
- scripts/lib/storage-state.sh 1011 B runs code
- scripts/verdict.sh 1.2 KB runs code
- test/fixtures/network_conditional_console.txt 45 B
- test/fixtures/network_fail.json 36 B
- test/fixtures/network_pass.json 67 B
- test/test_instance_detection.sh 1.6 KB runs code
- test/test_storage_state.sh 1.3 KB runs code
- test/test_verdict.sh 1.3 KB runs code
- test/test-df-ui-verify.sh 2.0 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.
- 9d ago First seen · 93 lines · 85 tokens per session scan A 1cfd4a79121d
df-ui-verify is a skill published in the GitHub repository OneDro1d/dark-factory (0 stars, last pushed today), licensed Apache-2.0. It adds 85 tokens to every session and 2,149 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-09-01.
Other skills, from other repositories
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.
test-warp-ui
Guides testing Warp UI features and changes using the computer use tool. Use this skill only when computer-use testing was requested (explicit request or accepted offer) and the computeruse tool is available to the agent. Covers launching Warp and verifying UI behavior.
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…
pyats-dynamic-test
Generate and execute deterministic pyATS aetest validation scripts - interface state, OSPF neighbors, BGP paths, ping matrices, and custom compliance tests. Use when writing a network test, validating post-change state, running pass/fail checks, or building automated regression tests.
test-loop
Plan, generate, and heal an executable E2E test suite from approved acceptance criteria (web and mobile).
playwright-cli
Automates browser interactions for testing and validating your own web applications using playwright-cli. Use when you need terminal-first browser control for navigation, form filling, screenshots, tracing, bound browser sessions, debugging, or generating Playwright test code. Only use against applications you own or…