Fingerprint CI Gate
Gate builds on browser fingerprint regressions — baseline scans, diffs, and CI failure on score drops
- What
- Gate builds on browser fingerprint regressions — baseline scans, diffs, and CI failure on score drops
- Cost
- Free
- Needs
- Node.js 22 or newer; a Chromium in the CI image (with enough shared memory for Chrome)
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — a measurement tool for testing your own browser automation harnesses: save a liarjs baseline fingerprint scan as JSON, diff later runs against it, and fail the CI job (GitHub Actions, GitLab CI, or other pipelines) when the consistency score falls below a floor — catching a regression in a Chromium build or scraping harness before it ships. Works via `npx [email protected]` (Node 22+, a Chromium in the image, zero runtime dependencies). By @liarjsdev, listed here with credit to its creator. Transparency: this is a measurement tool for your own harnesses — it measures fingerprints, it does not spoof or evade them; dual use is possible, as with any QA tooling. Honest caveats: the CI image needs enough shared memory for Chrome and the browser sandbox should stay enabled. Skill Harbor never reviews the code, review it yourself before use.
Version:
Quick answer
Fingerprint CI Gate is a free Muse skill that gates builds on browser fingerprint regressions for your own automation harnesses. It saves a liarjs baseline scan as JSON, diffs later runs against it, and fails CI when the score drops. That way fingerprint quality is asserted in the pipeline, not assumed or discovered late.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 4068c79Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Prerequisites: Node.js 22 or newer; a Chromium in the CI image (with enough shared memory for Chrome) Install "Fingerprint CI Gate" for me. Gate builds on browser fingerprint regressions — baseline scans, diffs, and CI failure on score drops Repository: https://raw.githubusercontent.com/liarjsdev/liarjs-skills/4068c79209753c74f895a4a5a6d117fcde8d94d1/skills/fingerprint-ci-gate/SKILL.md Pinned version: install the code at commit 4068c79209753c74f895a4a5a6d117fcde8d94d1 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file for the liarjsdev-fingerprint-ci-gate skill from the repository into a temporary folder 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "liarjsdev-fingerprint-ci-gate". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. any accounts, API keys, or CLI tools mentioned in the prerequisites above). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. Never ask me to paste secrets in chat — credentials go through the secure vault or environment variables. If anything looks off, stop and ask me.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 4068c79 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.