Practical Notes
Use this marketplace to standardize security work: the same checks, the same outputs, every time. In practice, set a rule that every risky change must pass at least one plugin run (and store the outputs as artifacts). Because skills can be powerful, always review what tools they invoke and what files they read/write.
Safety note: Install only trusted plugins and pin versions when possible; treat plugins as code in your threat model.
FAQ
Q: Is it open source? A: Yes. The repo is public; license is CC-BY-SA-4.0 (verified in Source & Thanks).
Q: Do I have to install everything? A: No. Add the marketplace, then install only the plugins you need.
Q: Where should I start? A: Pick one narrow plugin (e.g., insecure defaults) and run it on a small codebase first.