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 skills add Raidriar7170/hermes-skilleval --skill browser-smoke-testinggit clone --depth 1 https://github.com/Raidriar7170/hermes-skillevalWrote 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/raidriar7170/hermes-skilleval/browser-smoke-testing)<a href="https://agentmods.dev/skills/raidriar7170/hermes-skilleval/browser-smoke-testing"><img src="https://agentmods.dev/badge/skills/raidriar7170/hermes-skilleval/browser-smoke-testing/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/raidriar7170/hermes-skilleval/browser-smoke-testing"><img src="https://agentmods.dev/badge/skills/raidriar7170/hermes-skilleval/browser-smoke-testing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 6 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00021 | $0.00287 |
| Opus 5 | $0.00010 | $0.00143 |
| Sonnet 5 | $0.00004 | $0.00057 |
| Haiku 4.5 | $0.00002 | $0.00029 |
Grade A, and why
Browser Smoke Testing 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.
What it actually says
Browser Smoke Testing
Use after frontend or dashboard changes when a browser check is needed. Open the target URL, confirm the page is not blank, exercise the main interaction, and capture any visible error.
Evidence
- URL or file opened.
- Rendered page check.
- Interaction result or screenshot note.
Source Snapshot
Source: Browser plugin skill, local browser testing workflow
Short excerpt used for provenance, not a full source copy.
# Browser Use this skill for browser automation tasks such as inspecting pages,
navigating, testing local apps, clicking, typing, taking screenshots, and reading
visible page state. After setup, select the `iab` browser. Keep browser work in the
background by default. Show the browser when the
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 · 38 lines · 21 tokens per session scan A 725a9a89a2bd
Browser Smoke Testing is a skill published in the GitHub repository Raidriar7170/hermes-skilleval (124 stars, last pushed 1mo ago), licensed MIT. It adds 21 tokens to every session and 287 once invoked, about $0.0001 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-08-30.
Other skills, from other repositories
browser-testing
VERIFY your changes work. Measure CLS, detect theme flicker, test visual stability, check performance. Use BEFORE and AFTER making changes to confirm fixes. Includes ready-to-run scripts: measure-cls.ts, detect-flicker.ts.
browser-testing
Tests a real web user flow with a browser by asserting semantic behavior, network and loading states, keyboard access, responsive layouts, and stable visual evidence. Use for browser bugs, end-to-end UI behavior, responsive or accessibility checks, and screenshot baselines. Not for static source review without a…
web-ui-test
Test the IronClaw web UI using the Claude for Chrome browser extension.
browser-test-executor
Execute approved bounded browser Test DSL cases with fresh isolated contexts and auditable attempts. Use when running browser tests, reruns, regression checks, or blocked execution diagnostics.
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.
browse
Drive a real browser through Aside: open a page, read it, click through a flow, take screenshots, check console errors. (gstack).