name	iron-shield
description	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.
version	0.1.0
author	mmbnchips
license	CC0-1.0
compatibility	Hermes Agent skills system
metadata	{"hermes":{"tags":["shipping-now","hybrid","defense-and-recovery","defense","recovery","stabilization","survivability"],"homepage":"https://github.com/Hmbown/mmbnchips"}}

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.

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

Restate the target, success condition, and no-touch boundaries before you spend the chip.
Identify the specific frontal vector under sustained attack and audit all entry points along that surface.
Harden the vector with layered, durable defenses designed to hold under repeated impact without breaking.
Validate that the hardened surface withstands sustained adversarial testing and that coverage elsewhere has not been neglected.
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

/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

Más de este repositorio

mismo repositorio

black-barrier

Hmbown/mmbnchips

Use Black Barrier when ordinary buffering is too soft and thresholding alone is too permissive. The problem is not just one incoming hit, or a stream of weak noise, but contact that should have to prove itself before it reaches the work at all: ambiguous requests, half-authorized changes, untrusted touchpoints, speculative interruptions, or access that has not earned the right to cross the perimeter. Black Barrier establishes a denser selective shell around a critical surface. Unlike Barrier, it is not a one-hit absorb. Unlike Aura, it does not merely ignore weak impacts below a threshold. It enforces a stricter admission rule: only declared, validated, high-confidence contact gets through, and everything else is refused, deferred, or held outside until it can justify entry.

2026-04-110

curse-shield

Hmbown/mmbnchips

Use Curse Shield when Hermes should protect a surface in a way that makes contact linger on the attacker. The shield is not just there to absorb the next hit or throw an immediate counter; it tags hostile touch with a lasting penalty, mark, or contamination that follows the offender after impact. In practice, Curse Shield is for defended surfaces that impose audit burden, throttling, suspicion, reduced trust, quarantine, follow-up scrutiny, or another durable consequence on whatever keeps pressing into them.

Use Aqua Aura when the real threat is heat: escalating pressure, bursty contention, emotional overtemperature, or rapid-fire noise that is making clean operation impossible. Unlike a plain Aura that simply blanks weaker hits, Aqua Aura diffuses and cools them so Hermes can keep moving without matching the room's panic tempo.

2026-04-110

aura

Hmbown/mmbnchips

Use Aura when the problem is not one big blow but constant low-grade interference: nuisance traffic, shallow criticism, repetitive edge pokes, cheap probes, or background turbulence that keeps stealing turns. Aura sets a named threshold and blanks everything below it, so Hermes can keep operating through minor contact while preserving attention for impacts that actually matter. Unlike Barrier, Aura is not a one-hit absorb; unlike Leaf Shield, it does not punish contact. It is the baseline selective shell.

2026-04-110

name	iron-shield
description	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.
version	0.1.0
author	mmbnchips
license	CC0-1.0
compatibility	Hermes Agent skills system
metadata	{"hermes":{"tags":["shipping-now","hybrid","defense-and-recovery","defense","recovery","stabilization","survivability"],"homepage":"https://github.com/Hmbown/mmbnchips"}}

Iron Shield

Raise a durable frontal barrier that holds under sustained assault.

What This Skill Does

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

Restate the target, success condition, and no-touch boundaries before you spend the chip.
Identify the specific frontal vector under sustained attack and audit all entry points along that surface.
Harden the vector with layered, durable defenses designed to hold under repeated impact without breaking.
Validate that the hardened surface withstands sustained adversarial testing and that coverage elsewhere has not been neglected.
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

/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