USB+ / @peepsick/usb-cliPartly tested🌏 World

Check before you install a skill or MCP: PeepSick's USB+ uses secscan to compare a skill's claims with its body, and mcprobe to watch MCP servers without calling their tools

Skills and MCP servers are copy-pasted everywhere, and it is hard to know before install whether they read .env, shell out, or delete files. PeepSick Labs' USB+ (Universal Systems Bridge, GitHub PeepSick/usbplus, npm @peepsick/usb-cli, MIT) turns “inspect then install” into a CLI: usb secscan statically compares a skill's declared contract with capability signals in the body; usb mcprobe, with explicit consent, starts MCP servers for a handshake-only observation and does not call tools by default; it can also install from a 529-skill catalog into 16 runtimes. Chinese-community posts by @wlzh (and @MirrortekUK) covered the v1.0.8 trust layer on 9 Nov 2026. We installed @peepsick/[email protected]: usb version reported current/latest 1.0.8 and catalog “Universal Systems Bridge Catalog”; usb search postgres returned 16 hits; usb list listed 529 skills; secscan on two local demo skills flagged a sneaky skill whose friendly frontmatter hid .env reads and rm -rf (HIGH secrets-access, MEDIUM destructive-commands, exit 1); secscan --repo cloudflare/security-audit-skill also flagged an fs.rmSync signal in tests (MEDIUM). We did not run usb install for the full 529-skill pack, and did not run mcprobe --yes against a live MCP server.

Visit site USB+ / @peepsick/usb-cli ↗
Pricing
Free
Region
Global
Where it's from
Overseas
Added
Nov 10, 2026
Tested on
Nov 10, 2026
Version we used
@peepsick/[email protected]; usb-secscan v1.5.0; PeepSick/usbplus @ 103727e
Categories
CodingProductivityAutomation & Agents
Original author
M. @wlzh ↗
Our test
Partly tested
Cost / time
MIT/open source; the npm package is free. secscan is static and never executes a skill. mcprobe --yes starts local/network MCP processes (using those services' own resources) but does not call their tools. Installing all 529 skills uses disk and writes into agent dirs—prefer a single slug.
Source
X @wlzh ↗X @MirrortekUK ↗GitHub PeepSick/usbplus ↗npm @peepsick/usb-cli ↗

The task

Before dropping someone else's skill or MCP into Claude Code / Cursor, check that what it declares matches what the body (and, for MCP, startup) actually does.

Steps

  1. Install with npm install -g @peepsick/usb-cli, then usb version (we got 1.0.8). The site also documents a sha256-checked curl installer.
  2. Browse the catalog: usb search <query>, usb list, usb info <slug>. The default host is https://usbplus.peepsicklabs.com.
  3. Inspect before install: usb secscan ./path-to-skills for a local tree; usb secscan --system for installed locations; usb secscan --repo owner/repo (or a full GitHub URL) for a read-only remote scan. In CI, usb secscan --json . plus --write-baseline / --baseline fails only on new findings.
  4. To observe MCP startup, use usb mcprobe (dry-run without --yes first; then usb mcprobe --yes). Docs say probing may start processes or hit the network, needs explicit consent, and does not call tools by default.
  5. Only after a clean review, usb install <slug> or usb install --target=claude into a runtime. Bare usb install pulls all 529 skills—preview with --dry-run first.

Prompt

Install @peepsick/usb-cli and run usb secscan on the skill directory I am about to install. List HIGH/MEDIUM findings with file line numbers. Do not run usb install, and do not pass mcprobe --yes.

What the author says

@wlzh (9 Nov 2026): the pain is blind-installing skills/MCP; USB (Universal Systems Bridge) inspects first. After npm install -g @peepsick/usb-cli, usb install can place 529 skills into 16 runtimes. v1.0.8 trust layer: usb secscan statically diffs declarations vs body (.env reads, shell, deletes) with line numbers and CI hooks; usb mcprobe observes MCP startup without calling tools. @MirrortekUK posted a similar write-up the same day on “declared safe, actually risky” skills.

Our test

On 10 Nov 2026 we installed @peepsick/[email protected]; ran usb version / search postgres / list / info intent-router; built local demo-skill and sneaky-skill fixtures and ran usb secscan; also ran usb secscan --repo against https://github.com/cloudflare/security-audit-skill. Cloned PeepSick/usbplus @ 103727e for a read-only README check. Did not usb install into Claude/Cursor, and did not run mcprobe --yes.

What we found when we tried it:usb version: current=latest=1.0.8, catalog slug universal-skill-bridge-catalog. search postgres → 16 hits. list length 529. sneaky-skill: HIGH secrets-access + MEDIUM destructive-commands, exit 1. demo-skill (body said “do not touch .env”) also got HIGH secrets-access (PURPOSE-MISMATCH). Remote scan of security-audit-skill: MEDIUM destructive-commands from fs.rmSync in validate-coverage-ledger.test.cjs. Banner identifies usb-secscan v1.5.0 as static and non-executing.

How to get in

GitHub, npm and usbplus.peepsicklabs.com are globally reachable. Chinese write-ups: @wlzh and @MirrortekUK. CLI and site default to English.

Who it suits

People who paste skills/MCP from the internet and worry about a permission black box; teams that want inspection in CI. Skip if you only ever use skills you wrote yourself.

Pitfalls

  • secscan is a heuristic contract check, not a full security audit—it catches declaration mismatches and can miss things.
  • Our demo skill that only mentioned “don't touch .env” still got a secrets-access hit, so keyword sensitivity needs human context review.
  • mcprobe really starts MCP servers—dry-run first, then --yes; do not enable it around production credentials.
  • Bare usb install installs all 529 catalog skills; use --dry-run or a single slug.
  • The GitHub repo had ~1 star when we checked—judge by the npm package and reproducible CLI behavior, not stars.

More in this category