SKILLEMALL.ai

AD agent-browser

Browser automation for AI agents via inference.sh. Navigate web pages, interact with elements using @e refs, take screenshots, record video. Capabilities: web scraping, form filling, clicking, typing, drag-drop, file upload, JavaScript execution. Use for: web automation, data extraction, testing, agent browsing, research. Triggers: browser, web automation, scrape, navigate, click, fill form, screenshot, browse web, playwright, headless browser, web agent, surf internet, record video

modbender/skill-library-mcp Agent Skills author: modbender MIT 10 files · 3 scripts body ≈ 2 335 tokens Open the sourcegithub.com analyzed 2 d ago

Browser automation for AI agents via inference.sh. Navigate web pages, interact with elements using @e refs, take screenshots, record video. Capabilities: web…

As a process D 44/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions

IntegrationPlaywrightMedia and videoAI and agentstype and topics are labelled automatically from the skill text
JSON
Technical rating
A
92/100
safety, quality, tests
Safety 60%
95
Quality 40%
88
Run on models
none yet
Process rating
D
44/100
Unfinished process
Result and completion w 14
0
Inputs and preconditions w 11
0
Failures and branches w 10
0
the three weakest of ten parameters · all ten

What is at stake

Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.

Dangerous commands medium severity

Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.

If you install

The skill contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.

For the author

Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.

How to improve

    For the model run — optional
    • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
    • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

    Guard findings · 1

    ✓ No critical or high findings

    Medium and low: 1
    • medium Dangerous commands cmd-pipe-to-shell SKILL.md:23
      Downloads and executes remote code from an unrecognised host (pipe to shell) (the skill's own vendor host)
      curl -fsSL https://cli.inference.sh | sh && infsh login
      vendor-host

    Files scanned: 10. Evidence is masked. Grey chips explain why severity was lowered.

    Against the Agent Skills spec

    ✓ No remarks against the Agent Skills spec

    Process rating: all ten parameters 44/100

    • 0Result and completion. Does not say what the result is
    • 0Inputs and preconditions. Does not say what the process needs to start
    • 0Failures and branches. Linear process with no failure handling
    • 0Progress reporting. Says nothing while it works
    • 20When it triggers. No condition that starts the skill
    • 30Running it twice. 3 mutating operations with no state check
    • 40Consistency. Frontmatter name (agent-browser) differs from the folder (agentic-browser-0-1-2)
    • 85Steps. 12 steps, 3 vague phrases
    • 100Tools and files. Tools declared in frontmatter
    • 100Execution cost. Instruction body is 2335 tokens
    • low 12 top-level sections: this looks like several domains in one skill

    Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

    Quality signals

    • +5Description has no quoted example phrases that should trigger the skill
    • +4Description does not say when NOT to use the skill (false activations)
    • +3Output format is not stated: the model decides each time
    • +1No license
    • +2Single-language instructions
    • +3Description length 487: enough signal without eating the budget
    • +4Structure: 22 headings
    • +3Step-by-step instructions: 12 items
    • +4Has examples (13 code blocks)
    • +4Reference files are cited in the instructions (6 of 6)

    Quality base 70; lint remarks subtract, signals add up to 100. Result: 88.