updated 2026-09-29 16:10 UTC

BrowserSkill

Repository by Tencent

Let AI agents use your real, logged-in browser without interrupting your work. CLI + extension for browser automation across any shell-capable AI agent.

Agent Skills TypeScript Listed MIT

Is BrowserSkill safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard No result
Provenance None
Signed commits 29%
Last push today
Compare BrowserSkill

How does it stack up against its Agent Skills neighbours?

Pick any agent to compare →
Suggest a correction

In detail: BrowserSkill scores 25.1/100 (Grade D), ranked #349 of 359 tracked open-source AI agent projects, on evidence coverage D (1 of 5 independent signal types). The public evidence: no package-provenance attestation found; no OSSF Scorecard result yet; 29% of recent commits are signed; last pushed 2026-09-29. Every point is earned from checkable signals — never paid placement. How scoring works →

How BrowserSkill could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

How BrowserSkill compares in Agent Skills

  1. #347 Adversarial Spec 27.8 +2.7
  2. #348 Clawhub 25.6 +0.5
  3. #349 BrowserSkill 25.1 this agent
  4. #350 Skill Recorder 24.1 −1.0
  5. #351 Obsidian Skills 23.3 −1.8

Bars show each HVTrust score; the tick marks BrowserSkill’s 25.1.

Where the 25.1 comes from

HVTrust dimensions vs the Agent Skills average

25.1 / 100 · 50.0% confidence

BrowserSkill Agent Skills average (359 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
1.4 / 25
6.5 below avg 7.9
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
0.6 below avg 11.4
Transparency50% declared license · 50% OSSF Scorecard
8.5 / 17
3.6 below avg 12.1
Maintenance60% last-push freshness · 40% commit activity
20.0 / 20
5.7 above avg 14.3
AdoptionLog-scaled stars · package downloads
9.4 / 20
in line with avg 9.0

Quick Trust Read

What Would Improve It
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
2026-09-29
Newly Listed
First tracked at rank #349
Maintainer Checklist
Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Compare with another agent Get email alerts for BrowserSkill View Agent Skills Report missing data
86.2
Activity sub-score · out of 100
#349
In Agent Skills

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage D is separate — it grades how many independent signal types back the score (1 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-09-29 16:10 UTC · Repo last pushed today

Activity & Reach

Stars
7.9k
Forks
557
Last Push
2026-09-29
today
Commits (4 wk)
458
Downloads (7d)
—
HN mentions (30d)
—
Open Issues
32
Rank Change
NEW

Analysis

Activity Inputs

86.2 / 100
StarsRepository reach
23.4 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
12.8 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
—
Not available
Signed Commits
29%
of last 100 commits verified

Common questions about BrowserSkill

Public trust evidence for BrowserSkill is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does BrowserSkill publish package provenance?
No published build provenance is currently detected for BrowserSkill. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does BrowserSkill have an OpenSSF Scorecard?
No OpenSSF Scorecard data is currently published for BrowserSkill. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.
Is BrowserSkill actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does BrowserSkill use?
BrowserSkill ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are BrowserSkill's commits signed?
28% of the last 100 commits to BrowserSkill are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
None detected
No MCP server signal detected.
Detailed evidence is not shown in the public view.
External Service Dependencies
None detected
No clear third-party provider dependency detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
None detected
No clear plugin system or broad tool surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
N/A
No package source configured
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live

Maintain BrowserSkill?

For maintainers

HVTrust scores BrowserSkill from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Listed 1
2026-09-29
Newly Listed
First tracked at rank #349
GitHub →

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 25.1 Grade D
Markdown:
[![HVTrust](https://hvtracker.net/badge/browserskill.svg)](https://hvtracker.net/agents/browserskill)
HTML:
<a href="https://hvtracker.net/agents/browserskill"><img src="https://hvtracker.net/badge/browserskill.svg" alt="HVTrust"></a>

Other agents in Agent Skills

Data sources
GitHub REST API (repo, commits, stars, forks, license)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON