forge-armour

Hardens an audited Forge spec corpus by performing security posture analysis.

1|Updated Apr 18, 2026
One-click install
npx skills add https://github.com/GreyFlames07/forge --skill forge-armour
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: forge-armour
Source: https://github.com/GreyFlames07/forge/tree/main/.agents/skills/forge-armour
Command: npx skills add https://github.com/GreyFlames07/forge --skill forge-armour

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

Harden an audited Forge spec corpus to enforce explicit security postures, trust boundaries, and robust policies before implementation.

Core Features & Use Cases

  • Security posture review across project, module, and atom levels; builds a security profile; maps risks to concrete spec changes; proposes controls; writes only approved changes.
  • Ensures human approvals are required for any spec mutation and guards against silent changes.

Quick Start

Initiate a security posture review on the current spec corpus and propose approved Armour changes after an audit.

Frequently Asked Questions about forge-armour

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

FAQPage Schema
How do I harden a spec corpus for security before coding begins?

Harden an audited Forge spec corpus by performing security posture analysis across project, module, and atom levels. The process maps risks to concrete spec changes, proposes controls, and writes only approved changes to enforce explicit security postures.

What is security posture analysis for a specification corpus?

Security posture analysis reviews audited specifications to build a security profile and map identified risks to concrete spec changes. It ensures requirements for trust models, data handling, authentication, authorization, abuse resistance, and incident response are explicitly satisfied.

How do I ensure human approval is required for spec mutations during security hardening?

Ensure human approval for spec mutations by using a hardening process that guards against silent changes and writes only approved Armour changes. This guarantees no specification is altered without explicit human authorization during security posture improvements.

Can I apply security hardening at both project and module levels?

Apply security hardening across project, module, and atom levels for comprehensive coverage. The analysis builds a security profile and guides security posture improvements at each level, ensuring trust boundaries and robust policies are enforced throughout the spec corpus.

Do I need to run an audit before hardening my Forge specs?

Run an audit before hardening because the security posture analysis is applicable after forge-audit. The hardening process relies on an audited Forge spec corpus to accurately map risks to spec changes and propose effective controls.

What security requirements does spec hardening cover for trust models and data handling?

Spec hardening covers requirements for explicit trust models, data handling, authentication and authorization coverage, abuse resistance, incident response, and durability artifacts. It maps these requirements to concrete spec changes within the audited corpus.