pinchtab-stealth-score

Benchmarks Chrome and CloakBrowser against 15 bot-detection sites via Dockerized PinchTab agents.

10.2k|773|Updated Feb 15, 2026
One-click install
npx skills add https://github.com/pinchtab/pinchtab --skill pinchtab-stealth-score
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pinchtab-stealth-score
Source: https://github.com/pinchtab/pinchtab/tree/main/skills/pinchtab-stealth-score
Command: npx skills add https://github.com/pinchtab/pinchtab --skill pinchtab-stealth-score

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Measuring how detectable an automated browser is requires manually visiting dozens of fingerprinting and bot-detection sites and recording results by hand. This Skill automates that entire sweep, producing comparable metrics across browser builds.

Core Features & Use Cases

  • Automated stealth sweep: Drives PinchTab through 15 bot-detection and fingerprinting sites (sannysoft, creepjs, browserleaks, coveryourtracks, and more) using per-site English playbooks.
  • Side-by-side browser comparison: Runs chrome, cloak, or both in isolated Docker containers and generates a divergent-metrics table highlighting where the browsers disagree.
  • Historical tracking: Appends each comparison run to history.jsonl and regenerates a last-20-runs history.md table for cross-session trend analysis.
  • Use Case: After modifying CloakBrowser's fingerprint defenses, run the sweep to verify which detection signals changed relative to stock Chrome.

Quick Start

Ask the agent to run the stealth score comparison for both chrome and cloak browsers and show the divergent metrics table.

Frequently Asked Questions about pinchtab-stealth-score

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I test if my automated browser is detected as a bot?

Run the stealth-score sweep, which navigates the browser through 15 public bot-detection sites like sannysoft, creepjs, and browserscan. An agent captures per-site metrics such as webdriver flags, trust scores, and fingerprint hashes into a structured JSON report.

How to compare Chrome vs CloakBrowser fingerprint detection?

Run the skill with the 'both' argument to execute sequential Docker-based sweeps for chrome and cloak. The summarizer then prints a divergent-metrics table showing only the rows where the two browsers disagree on real values.

What bot-detection sites does the stealth score test cover?

The sweep covers 15 sites including sannysoft, rebrowser, iphey, whoer, browserscan, pixelscan, incolumitas, amiunique, browserleaks, creepjs, coveryourtracks, and fingerprint-demo. The list is defined in an editable index file, so sites can be added or removed without code changes.

Does the stealth score test require Docker?

Yes, Docker must be running because each browser benchmark executes inside an isolated PinchTab container bound to host port 9867. The up.sh script builds the image from current source and fails if the container does not become healthy.

Why does the stealth score show detection on cloak browser?

A non-zero detection score on cloak that matches chrome's baseline reflects a generic Chromium signal, not a CloakBrowser regression. The results are advisory rather than a CI gate, so compare divergent metrics against the chrome baseline before concluding a problem.

How long does a full stealth score run take?

Each browser sweep takes roughly 12-15 minutes once images are cached, so a both run takes about 25-30 minutes. First-time cloak image builds add approximately 10 minutes.