propose-security-hardening

Develop evidence-backed architectural security hardening proposals from vulnerability findings and source code.

Updated May 4, 2026
One-click install
npx skills add https://github.com/antstanley/skills --skill propose-security-hardening-antstanley
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: propose-security-hardening
Source: https://github.com/antstanley/skills/tree/main/plugins/security/skills/propose-security-hardening
Command: npx skills add https://github.com/antstanley/skills --skill propose-security-hardening-antstanley

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Individual vulnerability patches often leave the underlying structural weaknesses untouched, so the same class of flaw recurs. This Skill turns scan findings, vulnerability disclosures, incident reports, or source code into a decision-ready portfolio of structural and architectural hardening proposals with real options, tradeoffs, and migration plans. ## Core Features & Use Cases - Evidence-driven opportunity analysis: Clusters findings by violated invariant, trust boundary, and control ownership to identify high-leverage hardening opportunities, or honestly concludes that local remediation is preferable. - Multi-option design proposals: Produces per-opportunity proposals with before-and-after Mermaid diagrams, delta tables, and tradeoff analysis across security, performance, memory, reliability, operability, and migration dimensions. - Structured artifacts: Emits a machine-readable hardening.json, a skimmable hardening.md portfolio, per-opportunity proposal documents, and implementation work packages once an option is selected. - Use Case: After a security scan of an archive extraction module reveals several path traversal findings, use this Skill to evaluate whether to patch each call site, centralize containment behind one owned boundary, or introduce process isolation, complete with diagrams and a conditional recommendation. ## Quick Start Analyze the findings from my latest security scan and propose architectural hardening options with tradeoffs and diagrams.

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 security scan findings into an architecture improvement plan?

Provide the scan directory or findings to this Skill, which clusters evidence by violated invariants and trust boundaries, then develops qualified hardening opportunities into full proposals. Each proposal includes design options, tradeoff analysis, diagrams, and a conditional recommendation.

Can I propose security hardening without a completed security scan?

Yes. A directory of vulnerability disclosures, incident reviews, supplied findings, or relevant source code is a valid input. The Skill inventories the evidence directly and records missing scan metadata as a limitation rather than rejecting the input.

What artifacts does a security hardening analysis produce?

It produces a context.md evidence inventory, a structured hardening.json, a skimmable hardening.md portfolio, one proposal per qualified opportunity, Mermaid before-and-after diagrams per option, and an implementation plan only after you select an option.

Does the hardening proposal modify my source code automatically?

No. Source evidence and scan artifacts remain read-only, and implementation begins only after you select an option and explicitly request changes. The Skill then refreshes the source, checks for drift, and implements in reviewable phases.

What happens if no architectural hardening opportunity is justified?

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.