Verified:GitHub

security-designer-skill

Generate a security design package mapping threat models and controls to architecture artifacts.

Updated Jan 20, 2026

Search Tags:#authorization #authentication #data-protection #audit-logging #secrets-management #threat-model #security-design

Ready to run

npx skills add https://github.com/Galharel/my-codex-skills --skill security-designer-skill

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: security-designer-skill
Source: https://github.com/Galharel/my-codex-skills/tree/main/security-designer-skill
Command: npx skills add https://github.com/Galharel/my-codex-skills --skill security-designer-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Design and document security controls that align with architecture, backend, and data designs, ensuring threat models, authentication/authorization strategies, data protection, and operational controls are defined upfront.

Core Features & Use Cases

Threat modeling and risk assessment aligned to system design.
Authentication and authorization strategy definition, including session/token design.
Data protection planning (encryption, key management, audits) and operational controls.
Use Case: When designing a new service, produce a security design package that maps to architecture artefacts and data schemas.

Quick Start

Provide architecture and data design artifacts to generate a security design package that defines threat model, auth strategy, data protection, and operational controls.

Frequently Asked Questions about security-designer-skill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I design a security posture that maps threat models and access controls to architecture and data artifacts?▼

To design a security posture, you map threat models, authentication and authorization strategies, data protection, and operational controls directly to your architecture and data schemas. This process generates a comprehensive security design package defining access control, encryption, and auditing.

What is the best way to define authentication and authorization strategies across backend and data systems?▼

Defining authentication and authorization strategies requires mapping session and token designs to backend and data schemas. By aligning these strategies with architecture artifacts, you ensure access control mechanisms are consistently applied across all system components.

Do I need architecture and data schema packets to generate a security design package?▼

You need architecture and data schema packets to generate a security design package. The process requires docs/architecture.packet.json and docs/story-map.json or docs/prd.packet.json as fallback, while optionally using backend.design.packet.json and data.schema.packet.json inputs.

How do I plan data protection and operational controls like encryption and secrets management for a new service?▼

Planning data protection and operational controls involves defining encryption, key management, auditing, and secrets management across systems. This aligns operational safeguards with your architecture design to ensure comprehensive data security upfront.

Can I align threat modeling and risk assessment with my existing backend design documents?▼

You can align threat modeling and risk assessment with existing backend design documents. By processing backend.design.packet.json, the security design maps identified risks and operational controls directly to your pre-defined backend architecture artifacts.

What outputs do I get when generating a security design package for architecture and data contexts?▼

When generating a security design package, you get docs/security.design.packet.json and docs/security.design.md as outputs. These files document the threat model, auth strategy, data protection, and operational controls mapped to your architecture.