Loading the registry…
THE DEFAULT browser driver — invoke for ANY task driving a real browser, whether or not the user names it: E2E, QA, smoke, exploration, login-gated verification, resolving live selectors, plus team-workflow Phase 4 driving and Phase 4.5 exploration. Driver precedence: this skill FIRST → Playwright MCP only when its gate fails (say which condition) → claude-in-chrome only for the user's own logged-in Chrome profile. Reaching for a loaded browser MCP without running the gate is the known drift. Playwright still owns the committed `.spec.ts` suite — this drives, it is not a test framework. Headless login uses the encrypted Auth Vault, so the LLM never sees the password. Unattended runs (Phase 4/4.5, /team-run, scheduled) MUST have the dedicated E2E account + seeded test data in place BEFORE the first browser action — never invent credentials.
Claude Skills are markdown + scripts loaded into Claude Code; scanned with the same pipeline.
We found this by crawling public sources and nobody has attested to it. That is how most of the registry gets here, and it is not a mark against the artifact — it only means no authenticated act of publication is on record. An artifact can be the vendor's own and still appear here.
2 critical findings reported by agent-audit-kit. The composite score alone does not reflect this — read the per-scanner reports below.
Claude Skills install to a single target, no runtime picker.
nerlo install -- 'junjak/ai-harness (agent-browser-e2e)'
Manual alternative: copy the skill folder into ~/.claude/skills/ so Claude Code loads it on next launch.
cp -r -- 'junjak/ai-harness (agent-browser-e2e)' ~/.claude/skills/
Install respects the composite badge: Clean proceeds, Caution prompts for confirmation, and Flagged is refused. Write operations require an API token.
4 of 11 scanners examined this package. The rest do not apply to it — language, ecosystem and packaging decide which analyzers can say anything, and a scanner that cannot examine an artifact reports nothing rather than passing it.
v1.4.0
0 findings · 0.6s
v2.0.11
68 findings · 11.2s
v0.3.74
5 findings · 1.4s
v0.1.0
7 findings · 3.6s
v0.1.0
No source files this scanner can analyze were found in this artifact. What each scanner covers
0 findings · 3.6s
vv0.3.2
No Go packages were found in this artifact. What each scanner covers
0 findings · 0.1s
v0.1.0
This scanner found nothing in this artifact that it assesses. What each scanner covers
0 findings · 1.0s
No report in this scan: govulncheck, osv-scanner, trivy, trivy_image.
1 scan on record. Every scan's full results are retained immutably for 24 months.
| Completed | Composite | Change | Scanners | Status |
|---|---|---|---|---|
| Aug 18, 2026 | Scan Halted | — | agentshield: completecisco-skill-scanner: completeagent-audit-kit: completenerlo-behavioral ·n/a: not applicablenerlo-install-instruction: completecapslock ·n/a: not applicablenerlo-multi-source ·n/a: not applicable | rejected |
Findings in files this artifact installs stand as reported; a model re-read the rest and said which ones it believes are false positives. This is a second opinion published beside the evidence, not a correction to it: the per-scanner reports above are unchanged, every dismissed finding is still listed there at its original severity, and the score and the Flagged badge are computed from those raw severities alone. Nothing below moved them.
This review has not run for this scan yet. It runs once per scan, in the background, and is kept; it appears here when it has. Until then all 80 findings above stand exactly as their scanners reported them, at full severity.