Hi friends, I’ve been playing with agent skills lately and liked it very much. But reading all the research about the security issues got me worried since there is no “one official place” to get skills and giving my agents so 3rd party stuff might not be best idea. So I built “skillsio” (repo name: secure-skills), a hardened fork of Vercel’s skills installer. Same “nice UX” install flow, but with an extra layer: security scanning before install. I’ll be honest, it’s not great architecture or something but I think it’s a good project because its research based and deep UX/UI thinking (or forking in my case… shutout Vercel for a great tool) Repo: https://github.com/alonw0/secure-skills Command: npx skillsio add repo/skill NPM package: https://www.npmjs.com/package/skillsio What it does Scan for known suspicious patterns (rules based on public research) Extract + show outbound URLs found in the skill Optional deeper scan (AST-style / taint-style approaches depending on file types) Optional VirusTotal enrichment (BYO API key) Also you can add custom rules What it’s NOT Not a perfect security solution (not 100% or even 90%) Not “enterprise-grade” architecture Doesn’t replace code review / sandboxing It’s basically a pragmatic guardrail + visibility, designed to be hard to ignore I’d love feedback on: Rule ideas / false positives / missed patterns What you’d want in a “safe skills” workflow Whether “scan-first” should be default behavior in installers If you’re comfortable, drop a couple real skills you’ve installed (or links) and I’ll test the scanner and tune rules. submitted by /u/Rizlapp
Originally posted by u/Rizlapp on r/ClaudeCode