met-guard

Apply a directional guard to a single attack surface and document protected faces.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/Hmbown/mmbnchips --skill met-guard
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: met-guard
Source: https://github.com/Hmbown/mmbnchips/tree/main/generated/codex/met-guard
Command: npx skills add https://github.com/Hmbown/mmbnchips --skill met-guard

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Harden a single attack surface by applying a directional guard to a specific face. This approach is useful when omnidirectional protection is unnecessary and you need a targeted defense that reduces risk without over-guarding other surfaces.

Core Features & Use Cases

  • Directional shielding on one attack surface to block a known threat vector.
  • Clear documentation of protected vs. exposed faces to support audits and risk assessment.
  • Lightweight, reusable guard patterns that fit into broader security workflows (defense and recovery).

Quick Start

Provide a directional guard on the identified attack surface and document its coverage and gaps.

Frequently Asked Questions about met-guard

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

FAQPage Schema
How do I apply a directional guard to a single attack surface?

To apply a directional guard to a single attack surface, you name the specific face requiring defense, implement a minimal viable shield against identified threat vectors, and document which areas remain exposed.

What is directional shielding in threat modeling?

Directional shielding in threat modeling is hardening a specific attack surface by applying a targeted guard to block known threat vectors, leaving other unprotected faces intentionally unguarded to reduce unnecessary over-guarding.

When should I use targeted defense for risk management instead of omnidirectional protection?

Use targeted defense for risk management when threat vectors are identifiable and omnidirectional protection is unnecessary, allowing you to focus resources on risk-limited interfaces or endpoints while accepting exposure on other faces.

How do I document protected versus exposed attack surfaces for an audit?

Document protected versus exposed attack surfaces by recording the specific guarded face, the minimal viable shield implemented, and explicitly listing which interfaces remain unprotected to support risk assessment and audits.

Can I use minimal viable shields within broader security workflows?

Yes, you can use minimal viable shields within broader security workflows because these lightweight, reusable guard patterns integrate into defense and recovery processes without disrupting existing operations.

Why does threat modeling leave certain attack surfaces unguarded?

Threat modeling leaves certain attack surfaces unguarded when applying a directional guard to reduce risk on a specific face, accepting calculated exposure on other surfaces where threat vectors are not currently identifiable.