earlyink
056 first flagged10 Oct 2026 +7d · nothing yet

Agent skills need a package registry, and nobody runs one yet

Provenance, versioning and security scanning for SKILL.md files that coding agents run with user permissions.

Crowded · Skill supply-chain paper, 1,000-agent orchestration

Written for: Investor or analyst

Next step

Thesis: agent skills become a software supply chain with a security category on top, as npm packages did, within 18 months. Confirming signal: a disclosed malicious or backdoored SKILL.md affecting many repos, or GitHub announcing skill versioning. Already building: the Skill Constellations research authors, and MCP-layer tools such as Delta MCP nearby.

Why now

Skill execution is about to grow sharply. Claude can now run up to 1,000 parallel sub-agents (catching 66 of 70 hidden bugs against 27 for a single agent). Gemini agents get their own workplace identities. MCP proxies like Delta MCP are appearing to sit between apps and tools. npm's problems are repeating without npm's tooling. Budgets are not there yet. The first public malicious-skill incident would create them.

What became possible

A new study traces how developers copy agent skills between GitHub repositories. Those skills run with the user's permissions inside Claude Code and Codex, yet have no registry, no versions and no provenance, so nobody can tell where a fix reached or which repos need review.

Two ways in

  1. Skill provenance graph

    Maps copied skills across public and private repos, flags vulnerable or tampered versions, and pushes fixes to every copy.

    Customer
    AppSec teams at companies with heavy Claude Code or Codex use
    Model
    Per-developer SaaS, like software-composition-analysis pricing
  2. Signed private skill registry

    An internal registry where approved skills are signed and pinned, with agents blocked from running unsigned ones.

    Customer
    Platform engineering teams at large enterprises
    Model
    Enterprise licence

Competition

Crowded

The idea that nobody runs a skills package registry yet doesn't hold up. Public registries already exist: skills.sh, SkillsMP and TanStack Intent.

Full competition notes (14 competitors)

The idea that nobody runs a skills package registry yet doesn't hold up. Public registries already exist: skills.sh, SkillsMP and TanStack Intent. Sentry dotagents handles version pinning. JFrog, Chainguard and localskills.sh sell private, governed registries, and JFrog explicitly signs and scans skills on publish. Snyk, Mondoo, NVIDIA and several open-source projects already cover scanning, so the signed private registry idea runs straight into JFrog and Chainguard, which enterprise platform teams already buy from. The weakest spot in the market is enforcement and lineage, not storage. I found no product that reliably blocks Claude Code, Codex or Cursor from running unsigned skills at runtime, across every agent, on developer machines. Building that would mean hooking into each agent's skill loading, or using MDM and endpoint policy, and a registry by itself doesn't do it. Lineage is the other gap. StepSecurity already inventories the skills in repos and on laptops, but I saw nobody fingerprinting copied and modified skills across repos, tracing them back to the upstream version, and opening fix PRs on every copy. That is roughly Dependabot for vendored skills. So the provenance graph idea has a narrow opening if it is built around matching copies whose content has drifted from the original, which matters because skills are mostly copied and pasted rather than installed. The risk is that Snyk, StepSecurity, JFrog or GitHub add this as a feature. Trail of Bits has reportedly shown bypasses against current scanners, so better detection quality could also set a newcomer apart, but scanning alone is already a commodity.

  • JFrog Agent Skills Registry and Skill Scanner

    Central registry for governing skills across agent tools. Publishing includes scanning and signing, and a beta Skill Scanner checks skill packages for malicious or suspicious behavior when they are uploaded. This overlaps directly with the signed private registry idea and comes from an incumbent that enterprises already use for artifacts.

  • Chainguard Skills Registry

    Chainguard's registry installs skills into agent directories such as .claude/skills. Chainguard already sells trusted, provenance-focused supply chain products to enterprises.

  • localskills.sh

    A hosted private skill registry with organizations, roles, SSO and audit logs. It also covers self-hosted and git-based options.

  • Snyk Agent Scan

    Scans skills and MCP servers on developer machines and can report to a central Snyk instance for company-wide monitoring. Snyk also published research on how common vulnerable skills are.

  • StepSecurity skill inventory

    Inventories the agent skills found in GitHub repositories and on developer machines. This is the closest existing product to the provenance graph idea's discovery layer.

  • Vercel skills CLI and skills.sh

    A public registry and npx installer that handles installing, discovering and updating skills across 40+ coding agents.

  • Sentry dotagents

    Beta tool that declares skill dependencies in agents.toml and locks versions so installs are reproducible. It is effectively a package manager with pinning.

  • TanStack Intent registry

    Indexes SKILL.md files that ship inside npm packages, so it uses npm for versioning and distribution.

  • SkillsMP

    A directory that calls itself the npm registry for agent skills. It claims 400k+ SKILL.md packages, a figure I have not verified.

  • Mondoo skillcheck

    Searches across tens of thousands of skills and scans them for hidden prompt injection.

  • SkillScan

    Open-source CLI that combines static YARA rules, an LLM dry run and a Docker sandbox with canary files. It outputs SARIF for GitHub.

  • Superagent skill-security

    Open-source scanner that uses regex, AST and taint analysis, with a separate step for judging intent.

  • skillhub

    Open-source Python CLI that lints, searches and installs skill packs from a curated registry.

  • skrun

    Open-source Node CLI that imports and syncs skills across Claude Code, Cursor and OpenCode.

Checked 2026-10-10

Risks

  • GitHub or the labs build a native skill registry and absorb the category
  • There are no budgets until a public incident happens
  • Skill formats may change too quickly to standardise

Strong tech readiness and open space; market pull is the weak point (5).

tech 8 · pull 5 · space 8 · fit 8 · build 8

Exposed

Companies that could benefit or be threatened. News and context, not investment advice.

Momentum of its main topic

168 developments this week +53 vs last week
21 Sep: 0 developments22 Sep: 0 developments23 Sep: 0 developments24 Sep: 0 developments25 Sep: 0 developments26 Sep: 0 developments27 Sep: 0 developments28 Sep: 0 developments29 Sep: 0 developments30 Sep: 0 developments1 Oct: 0 developments2 Oct: 0 developments3 Oct: 0 developments4 Oct: 0 developments5 Oct: 0 developments6 Oct: 0 developments7 Oct: 0 developments8 Oct: 32 developments9 Oct: 26 developments10 Oct: 13 developments11 Oct: 11 developments12 Oct: 14 developments13 Oct: 19 developments14 Oct: 24 developments15 Oct: 35 developments16 Oct: 31 developments17 Oct: 15 developments18 Oct: 14 developments19 Oct: 23 developments20 Oct: 26 developments
Stage: Coverage

Sources

  1. Skill Constellations: Tracing the Supply Chain of Agent Skills on GitHubHF Daily Papers
  2. Anthropic's Claude can now orchestrate up to 1,000 AI agents in parallel through dynamic workflowsThe Decoder
  3. Google brings agentic AI to Gemini, starting with businessesTechCrunch AI
  4. mcpdelta/mcpdeltaGitHub

What happened next

  • +7d · 17 Oct 2026 nothing yet. No new product launches, funding rounds, acquisitions, or significant coverage directly addressing agent skills registry or security provenance were found after October 10, 2026. Relevant products in this space (AIR, Google Cloud Agent Registry, TrueFoundry Skills Registry) all launched or announced funding before the flag date.

How the record works

Status history

  • 2026-10-10 Flagged as buildable