opsec-discipline

仓库创建 2026年5月19日最近提交 24 天前SkillHot 收录 21 天前

▸ 精选理由

强调先考虑监测与清除，适合需降低检测风险的攻防团队。

▸ 风险提示

提供规避检测建议，可能被用于恶意规避检测与滥用。

这个 Skill 做什么

在实施任何外部行动前评估检测面、清理与机密脱敏的 OPSEC 指南。

在采取任何对外动作前，先评估这步操作会产生哪些可被检测的痕迹，如何清理和对敏感信息做脱敏。适用于要发起请求、部署 payload、侧向移动、外联或把抓到的流量喂给模型等高风险动作前。特别强调每种攻防手法都会有对应的 telemetry/检测签名，所以先选更“安静”的路径并预先规划清理流程。

▸ 展开 SKILL.md 英文原文

Use when about to take any outward or offensive action (request, payload, persistence, lateral movement, exfil, or feeding captured traffic to the model) — to decide detection footprint, cleanup, and secret redaction first

Skill 开发管理OPSEC清理策略检测评估通用

326

Stars

Forks

仓库内 Skill

+15

7 日增星

安装 / 使用

给你的 Agent 一句话（通用）

帮我安装这个 skill：https://raw.githubusercontent.com/hypnguyen1209/offensive-claude/main/skills/opsec-discipline/SKILL.md

或 curl 直取 SKILL.md

curl -fsSL "https://raw.githubusercontent.com/hypnguyen1209/offensive-claude/main/skills/opsec-discipline/SKILL.md"

SKILL.MD 节选查看完整文件 ↗

# OPSEC Discipline

## Overview

Decide the detection footprint and cleanup **before** acting, not after. Every offensive technique
in this repo pairs with the telemetry it generates and a detection signature — use that pairing to
choose the quieter path and to know what you'll need to clean up.

## Before acting, answer three questions

1. **Detection** — what telemetry does this generate? Which Sigma/EDR rule would catch it? (Each
   domain skill's OPSEC & Detection table has this.) Pick the lower-noise variant when one exists.
2. **Cleanup** — what does this touch (files, registry, services, accounts, tickets)? How is it
   reverted? Stage the cleanup before you create the artifact.
3. **

via SKILL·HOT · 数据来自 GitHub 公开信息 · 原文版权归作者所有