securability-engineering

Applies FIASSE/SSEM principles to generated, scaffolded, and refactored code for inherent security.

2|Updated Mar 17, 2026

Search Tags:#transparency #code-generation #trust-boundaries #secure-by-default #securable #FIASSE #SSEM

Ready to run

npx skills add https://github.com/Securability-Engineering/securable-claude-plugin --skill securability-engineering

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: securability-engineering
Source: https://github.com/Securability-Engineering/securable-claude-plugin/tree/main/skills/securability-engineering
Command: npx skills add https://github.com/Securability-Engineering/securable-claude-plugin --skill securability-engineering

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Meta-skill that wraps code generation to enforce FIASSE securable coding attributes and principles. Use when generating, scaffolding, or refactoring code so that the output is engineered to be inherently securable by default. Applies the nine SSEM attributes (Analyzability, Modifiability, Testability, Confidentiality, Accountability, Authenticity, Availability, Integrity, Resilience), the Transparency principle, and FIASSE defensive coding practices to every code generation task.

Core Features & Use Cases

Wraps built-in code generation capability by applying FIASSE/SSEM principles as engineering constraints to ensure securable output from the start.
Applies the nine SSEM attributes, the Transparency principle, and FIASSE defensive coding practices to every code generation task.
Use cases include generating, scaffolding, or refactoring code to be securable by default, especially for security-sensitive components (authentication, data handling, APIs) and trust boundaries.

Quick Start

Provide a secure-generation request to guide Claude Code to apply FIASSE/SSEM constraints to the output.

Frequently Asked Questions about securability-engineering

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

FAQPage Schema

How do I generate code that is secure by default?▼

To generate secure-by-default code, you can apply FIASSE/SSEM principles as engineering constraints during generation, scaffolding, or refactoring to ensure securable output from the start.

What are the SSEM attributes for securable software engineering?▼

The nine SSEM attributes for securable software engineering are Analyzability, Modifiability, Testability, Confidentiality, Accountability, Authenticity, Availability, Integrity, and Resilience.

Can I use FIASSE principles to refactor existing code for better security?▼

Yes, applying FIASSE defensive coding practices and the Transparency principle to refactoring tasks enforces robust dependency hygiene and securable attributes across trust boundaries.

What is the best way to enforce security boundaries in generated code?▼

Enforcing security boundaries in generated code is best achieved by applying the Transparency principle and FIASSE defensive coding practices to ensure robust dependency hygiene across trust boundaries.

Does this approach work for scaffolding authentication and data handling components?▼

Yes, applying FIASSE/SSEM constraints is specifically suited for scaffolding security-sensitive components like authentication, data handling, and APIs to ensure they are securable by default.

Why should I apply securable coding constraints during code generation instead of after?▼

Applying securable coding constraints during generation ensures the output is engineered to be inherently securable by default, preventing vulnerabilities from being introduced rather than fixing them later.