Security
# Security Module
Use this for perimeter, secrets, third-party intake and production-facing readiness.
Check:
- public exposure;
- admin/internal routes;
- secrets handling;
- scanners and logs;
- accepted risks;
- rollback and incident readiness.
Do not call the project secure. Return practical gates and missing evidence.when to use it
Community prompt sourced from the open-source GitHub repo Gudvin82/vibe-coding-protocols (NOASSERTION). A "Security" style prompt — adapt the placeholders and specifics to your task. Imported as-is and not independently retested here, so check the output before relying on it.
tags
roleplaycommunitygeneral
source
Gudvin82/vibe-coding-protocols · NOASSERTION