# Iron Shield

> Use Iron Shield when a public-facing surface, endpoint, or interface needs durable, ongoing protection against repeated attacks on the same vector. Unlike a one-time absorb or a brittle guard, Iron Shield maintains a sustained defensive posture that endures multiple impacts from the front.

- Skill: `hmbown/iron-shield-2` (Agent Skill)
- Install (CLI): `npx skillmds@latest add hmbown/iron-shield-2`
- Raw SKILL.md: https://api.skillmd.com/api/skills/hmbown/iron-shield-2/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Coding & Dev Tools
- License: CC0-1.0
- Author: Hmbown (https://skillmd.com/u/hmbown)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/hmbown/iron-shield-2

---

# Iron Shield
Raise a durable frontal barrier that holds under sustained assault.
## What This Skill Does
Use Iron Shield when a public-facing surface, endpoint, or interface needs durable, ongoing protection against repeated attacks on the same vector. Unlike a one-time absorb or a brittle guard, Iron Shield maintains a sustained defensive posture that endures multiple impacts from the front.
In this chip pack, Iron Shield is treated as a hybrid battle-chip procedure with a shipping-now delivery profile.
Canonical reference input: Iron Shield.
Hermes shelf: [Defense and Recovery](../DESCRIPTION.md).
## When To Use

- A public endpoint, API surface, or input boundary faces repeated adversarial traffic and needs sustained hardening.
- You need to reinforce a single attack vector that has already been hit more than once and will keep getting hit.
- Basic shield-level protections have been applied but are not durable enough for the volume of incoming abuse.

## Prerequisites

- Name which part of this move is real tool use versus battle-chip framing before you act.
- These procedures rely on the normal tools already present in the active Hermes runtime; this repo does not ship a separate integration layer.

## Procedure

1. Restate the target, success condition, and no-touch boundaries before you spend the chip.
2. Identify the specific frontal vector under sustained attack and audit all entry points along that surface.
3. Harden the vector with layered, durable defenses designed to hold under repeated impact without breaking.
4. Validate that the hardened surface withstands sustained adversarial testing and that coverage elsewhere has not been neglected.
5. Package the result with concrete evidence, what stayed untouched, and the next recommended chip only if follow-up is truly needed.

## Deliverables

- A hardened, directional defensive configuration protecting the identified frontal surface against repeated abuse.
- A durability report confirming the shield holds under sustained load and documenting what it does and does not cover.

## Pitfalls / Guardrails

- Keep the theatrical framing, but name the concrete mechanism that makes the chip useful right now.
- Iron Shield protects one direction. Flanks and rear remain exposed; do not assume full perimeter coverage.
- A shield that stays raised indefinitely becomes a wall. Set clear conditions for when the defensive posture relaxes.
- Do not use Iron Shield when a single absorb-and-clear is sufficient — use Barrier for transient threats.
- Keep the chip metaphor anchored to a real operating move; do not let flavor substitute for procedure.

## Verification

- Check that the response includes every promised deliverable and leaves an inspectable audit trail.
- Check that confirmed facts, assumptions, and proposed follow-up are visibly separated.
- Check which parts are concrete actions versus framing, so the operator can tell what is real now.

## Example Invocation
```text
/iron-shield harden a public-facing surface against sustained, repeated attacks on the same vector: apply durable layered defenses designed to hold under continuous impact, and verify the shield endures
```