Menu

1 / 3

I statically scanned 618 public agent skills. Here's what the scanner actually found

DEV Community: security·Vyankatesh·about 17 hours ago
#9R8KYy8S
#devtosecurity#devto#dev#skills#skill
Long article (640 words) — no AI summary yet.
Reading 0:00
15s threshold

Disclosure: I ran this study with an AI assistant (Claude), which wrote the scripts, did the analysis and drafted the paper. The assistant also did the manual spot-check described below, so that part is not an independent human review. Everything here is aggregate: no skill, author or repo is named.

Agent skills are folders of instructions (a SKILL.md ) plus optional scripts that coding agents load on demand. The text is read by the model as trusted guidance, and the scripts can run with your permissions. That makes public skill collections a supply-chain surface. So I asked a simple question: how risky do public skills look to a static scanner?

What I did

Found public GitHub repos by topic ( agent-skills , claude-skills , claude-code-skills ), then drew a seeded, stratified sample across four star ranges (0-9, 10-99, 100-999, 1000+).

Collected 622 skills from 387 repos. Nothing was installed, imported or run.…

Continue reading — create a free account

Join HashtagPLUS to read full articles, follow hashtags, vote, and join the conversation.