Browse the advisory list ›
| skill | advisory |
|---|
Agents install tools from places you don’t control. truecopy poison-scans every skill & MCP server, pins the vetted bytes into a lockfile, and fails the build if anything drifts. Below is the scan itself — run weekly, published raw, nothing hidden.
Each card says exactly what it is. A live card refreshes from the public weekly scan; an audit card is a dated point-in-time run; a scheduled card is a watch we haven’t stood up yet — we don’t show a scan we didn’t run.
| skill | advisory |
|---|
A single deterministic sweep of the entire registry — not a live feed. Read the write-up: the marketplace that started the panic →
OpenAI’s Plugin directory (formerly apps / connectors) is MCP-based — the same tool-schema surface truecopy scans. No scan has run yet; the watch goes live once truecopy introspects and poison-scans it. We won’t publish a directory size we can’t independently verify.
Hermes skills use the SKILL.md (agentskills.io) format truecopy already
reads, so it’s the next watch we’ll stand up. Its registries are community-maintained; we’ll
publish counts only from our own scan.
Source of truth: the public watch branch
— every number here is fetched live from
results.json.
truecopy.lock (optionally signed).truecopy verify exits non-zero before it loads.watch branch. This board reads that.Advisory ≠ poisoned. An advisory is a cautionary heuristic flag (e.g. “references a sensitive path”) worth a human glance — not a detection of malice. Confirmed-poisoned is the count that matters, and across the directory it stays at zero.
npm i -g @askalf/truecopy
truecopy add --claude --claude-plugins --sign # vet + pin every skill you can see
truecopy verify # CI: exit 1 on drift or poison