opsec-operational-discipline skillA
opsec-operational-discipline is agent-read markdown (skill) from miosa-osa/osa: Operational security for offensive engagements: OPSEC level tiers (silent/covert/loud) with detection-event budgets, cooldown and jitter mechanics, traffic blending, log sanitization, IOC tracking, abort-recommendation logic, and cleanup-on-completion. Use when planning how noisy an engagement should be, tuning scan/exploit pacing to avoid detection, responding to detection events during an engagement, or sanitizing logs and reports before delivery. Derived from the T3MP3ST platform's OPSEC cont.
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# OPSEC — Operational Discipline Derived from T3MP3ST's `src/opsec/index.ts` (Apache-2.0). OPSEC is a configuration, not a vibe: pick a level, budget your detections, and act on the signals. ## 1. The three OPSEC levels | Level | max detection events | cooldown after detection | jitter range | traffic blending | log sanitization | cleanup on complete | |---|---|---|---|---|---|---| | `silent` | 1 | 300 000 ms (5 min) | 5 000–15 000 ms | yes | yes | yes | | `covert` (default) | 3 | 60 000 ms (1 min) | 1 000–5 000 ms | yes | yes | yes | | `loud` | 20 | 2 000 ms | 100–500 ms | no | no | no | - **silent**: CTF/lab work or engagements where a single detection ends the mission. One detection event → long cooldown. - **covert**: the default for authorized engagements. Small jitter between actions, blending on, three detections before reconsideration. - **loud**: only for engagements where the operator has explicitly accepted detection (purple-team exercises, detection-validation runs). No blending, no sanitization, cleanup off — the point is to be seen. ## 2. Detection events and the abort recommendation …
Read the whole file at its exact version.
How to install
mdr add miosa-osa/osa/opsec-operational-discipline@git:20260913.e13b6b8mdr add miosa-osa/osa/opsec-operational-discipline@sha256:4d8fa3c34128b7a5Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_b3zmcns4leiosp3q)
1 badge views in 30 days
Versions
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (4951 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
miosa-osa/osa · 74 stars · license NOASSERTION · pushed 2026-09-24 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_b3zmcns4leiosp3q GET https://markdownregistry.com/api/v1/resolve?ref=miosa-osa/osa/opsec-operational-discipline GET https://markdownregistry.com/api/v1/blob/4d8fa3c34128b7a564f19cee7deaef4d81bad0827099810c67712df3496c48d1
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.