Browser Fingerprint Audit
Audit a browser fingerprint for internal contradictions — canvas, WebGL, fonts, WebRTC, timezone, scored 0–100
- What
- Audit a browser fingerprint for internal contradictions — canvas, WebGL, fonts, WebRTC, timezone, scored 0–100
- Cost
- Free
- Needs
- Node.js 22 or newer; a local Chrome, Chromium, or Edge (set LIARJS_CHROME if none is found)
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — a full fingerprint audit for browsers you control: the liarjs CLI probes canvas, WebGL/WebGL2/WebGPU, audio, 220 fonts, WebRTC, and timezone, then scores the fingerprint against the TLS/HTTP/ASN view of the same request — reporting every place the two stories disagree. Score starts at 100: 85+ is Trustworthy, 60+ Suspicious, below is Likely spoofed/bot. Supports --offline (JS-layer checks only, no outbound request) and --json for baselines. By @liarjsdev, listed here with credit to its creator. Transparency: a measurement tool for your own browsers and profiles — it audits consistency, it doesn't create spoofed profiles. Honest caveats: needs Node 22+ and a local Chrome, Chromium, or Edge; set LIARJS_CHROME if no browser is found. Skill Harbor never reviews the code, review it yourself before use.
Version:
Quick answer
Browser Fingerprint Audit is a free Muse skill that audits a browser fingerprint for internal contradictions, covering canvas, WebGL, fonts, WebRTC and timezone, scored zero to one hundred. For browsers you control, the liarjs CLI probes canvas, WebGL, WebGPU, audio, fonts, WebRTC and timezone, then scores the fingerprint against the TLS, HTTP and ASN view of the same request.
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 local Chrome, Chromium, or Edge (set LIARJS_CHROME if none is found) Install "Browser Fingerprint Audit" for me. Audit a browser fingerprint for internal contradictions — canvas, WebGL, fonts, WebRTC, timezone, scored 0–100 Repository: https://raw.githubusercontent.com/liarjsdev/liarjs-skills/4068c79209753c74f895a4a5a6d117fcde8d94d1/skills/browser-fingerprint-audit/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-browser-fingerprint-audit 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-browser-fingerprint-audit". 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.