skills.rest
openai
openaiOFFICIAL
Explore all skills by this author →
WebsiteGitHub

propose-security-hardening

Develop evidence-backed structural security hardening proposals from vulnerability findings and scan results.

5.3k|765|Updated Mar 4, 2026
Search Tags:#architecture review#vulnerability analysis#Threat Modeling#security hardening#remediation planning#tradeoff analysis#security design
One-click install
npx skills add https://github.com/openai/plugins --skill propose-security-hardening
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: propose-security-hardening
Source: https://github.com/openai/plugins/tree/main/plugins/codex-security/skills/propose-security-hardening
Command: npx skills add https://github.com/openai/plugins --skill propose-security-hardening

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Individual vulnerability patches often leave the underlying architectural weaknesses untouched, so the same class of security failure recurs. This Skill turns vulnerability disclosures, supplied findings, incident documents, source code, or completed Codex Security scans into a decision-ready portfolio of structural and architectural hardening options with explicit tradeoffs.

Core Features & Use Cases

  • Opportunity Analysis: Clusters evidence by violated invariants, trust boundaries, and control ownership to identify high-leverage structural improvements, or honestly concludes that local remediation is preferable.
  • Option Development with Tradeoffs: Produces meaningfully different design alternatives with before-and-after Mermaid diagrams, delta tables, and assessments across security, performance, memory, reliability, operability, and migration dimensions.
  • Structured Artifacts: Writes a distributable portfolio (hardening.md, hardening.json, per-opportunity proposals, diagrams) and an implementation handoff plan once an option is selected.
  • Use Case: After a Codex Security scan reports several findings sharing a common root cause, use this Skill to generate a design-review-ready proposal comparing a baseline local-guards fix against a centralized enforcement boundary, complete with residual risk analysis and a migration plan.

Quick Start

Use the propose-security-hardening skill to analyze the findings in this scan directory and produce a hardening proposal portfolio with design options and tradeoffs.

Frequently Asked Questions about propose-security-hardening

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

FAQPage Schema
How do I turn vulnerability scan findings into an architecture hardening plan?▼

Provide the scan directory, disclosure documents, or findings as input. The skill clusters evidence by violated invariants and trust boundaries, develops distinct design options with tradeoff analysis, and writes a portfolio with proposals, diagrams, and a recommendation.

Does this skill require a completed Codex Security scan to work?▼

No. A directory of vulnerability disclosures, incident reviews, or supplied findings is a valid input on its own. Scan metadata such as manifests and coverage receipts is used as additional evidence when available, but missing scan artifacts are recorded as limitations rather than blocking analysis.

What output artifacts does the security hardening analysis produce?▼

It writes a hardening directory containing context.md, hardening.json, hardening.md, one proposal per qualified opportunity under proposals/, before-and-after Mermaid diagrams under diagrams/, and an implementation plan only after you select an option.

Will the skill modify my source code automatically?▼

No. Source evidence and scan artifacts remain read-only, and implementation changes happen only after you select an option and explicitly ask for code changes. The analysis is a derived design product, not an automatic remediation.

What happens when no architectural hardening opportunity is found?▼

The skill records a local_remediation_preferred assessment with an empty opportunity list and explains why proportionate tactical fixes are the right outcome, rather than manufacturing an architectural proposal.

Related Skills

Explore More Software Engineering Skills→
overthetopseooverthetopseo
375

oss-forensics-orchestration

Coordinate multi-agent OSS forensics investigations across public GitHub repositories.

Community
Advanced
japurcelljapurcell

plan-tasks

Break down project work into verifiable tasks with acceptance criteria and dependency ordering.

Community
Intermediate
sjinkssjinks

security-review-owasp-django-rest-framework

Review Django REST Framework applications for OWASP security weaknesses.

Community
Advanced
entireioentireio
208

address-findings

Fetch open Entire trail findings, apply fixes, and mark them resolved.

Official
Intermediate