Strix Code Vulnerability Scan
usestrix/strix
Runs a Strix white-box security review that reads the source, then exploits what it finds in a sandbox so each reported issue has a proof-of-concept.
IoM Operational Security (OPSEC) advisor. An agent skill from chainreactors/malice-network.
Install Iom Opsec
$ npx skills add chainreactors/malice-network --skill iom-opsec -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install chainreactors/malice-network iom-opsec --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/chainreactors/malice-network.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/iom-opsec .claude/skills/iom-opsec && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "iom-opsec" agent skill from https://github.com/chainreactors/malice-network/tree/dev/skills/iom-opsec into .claude/skills/iom-opsec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iom-opsec", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/chainreactors/malice-network/tree/dev/skills/iom-opsecType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add chainreactors/malice-network --skill iom-opsec -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install chainreactors/malice-network iom-opsec --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/chainreactors/malice-network.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/iom-opsec .agents/skills/iom-opsec && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "iom-opsec" agent skill from https://github.com/chainreactors/malice-network/tree/dev/skills/iom-opsec into .agents/skills/iom-opsec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iom-opsec", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add chainreactors/malice-network --skill iom-opsec -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install chainreactors/malice-network iom-opsec --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/chainreactors/malice-network.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/iom-opsec .cursor/skills/iom-opsec && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "iom-opsec" agent skill from https://github.com/chainreactors/malice-network/tree/dev/skills/iom-opsec into .cursor/skills/iom-opsec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iom-opsec", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/chainreactors/malice-network.git --path skills/iom-opsec--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add chainreactors/malice-network --skill iom-opsec -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install chainreactors/malice-network iom-opsec --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/chainreactors/malice-network.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/iom-opsec .gemini/skills/iom-opsec && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "iom-opsec" agent skill from https://github.com/chainreactors/malice-network/tree/dev/skills/iom-opsec into .gemini/skills/iom-opsec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iom-opsec", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install chainreactors/malice-network iom-opsecInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add chainreactors/malice-network --skill iom-opsec -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/chainreactors/malice-network.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/iom-opsec .github/skills/iom-opsec && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "iom-opsec" agent skill from https://github.com/chainreactors/malice-network/tree/dev/skills/iom-opsec into .github/skills/iom-opsec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iom-opsec", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add chainreactors/malice-network --skill iom-opsec -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install chainreactors/malice-network iom-opsec --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/chainreactors/malice-network.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/iom-opsec .opencode/skills/iom-opsec && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "iom-opsec" agent skill from https://github.com/chainreactors/malice-network/tree/dev/skills/iom-opsec into .opencode/skills/iom-opsec/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "iom-opsec", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
iom-opsec- GitHub stars
- 500
- Token cost
- ~1.4k tokens
- SKILL.md length
- 580 words
- Files
- 3
- Skills in repo
- 2
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
IoM Operational Security (OPSEC) advisor. An agent skill from chainreactors/malice-network.
- Works in 4 steps: Identify the security products in the… → Search the case library for -.md → If a matching case exists, cite the… → …
- Conditions: use when the user asks is this safe?
- SKILL.md covers Methodology: Five Questions…, HITL Decision Framework, Case Library and References
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Iom Opsec is an agent skill from chainreactors/malice-network. IoM Operational Security (OPSEC) advisor. Provides OPSEC methodology guidance, helps users understand operational risks, build secure operating habits, and accumulate experience through a case library. Does not execute commands directly; serves as decision support. Concrete technical specifications and OPSEC scoring are maintained in the iom-pentest skill. Trigger conditions: use when the user asks "is this safe?", "will this be detected?", "how should I think about OPSEC?", "risk assessment", "operational…
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files (for example `reference/case-template.md` and `reference/cases/cred-dump-defender.md`).
It sits in Security, covering Penetration testing. The repository describes itself as: Next Generation C2 Framework, IoM-server/client. The licence is Apache-2.0.
When your agent uses it
- Conditions: use when the user asks is this safe?
- Will this be detected?
- How should I think about OPSEC?
- Risk assessment
Example prompts
- “is this safe?”
- “will this be detected?”
- “how should I think about OPSEC?”
- “/iom-opsec”
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Identify the security products in the target environment
- Search the case library for -.md
- If a matching case exists, cite the historical conclusion and skip techniques known to fail
- If no matching case exists, assess per the methodology, execute, and record the result as a new case
What it can do on your machine
Read from SKILL.md and the folder at commit 6c0e358. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Iom Opsec loads about 1.4k tokens when it runs. Until then it costs about 146 tokens; SKILL.md has 580 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from chainreactors/malice-network at commit 6c0e358, republished under its Apache-2.0 licence (© chainreactors). 580 words, ~1,414 tokens.
Download SKILL.mdSave it as
.claude/skills/iom-opsec/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- iom-opsec
- description
- IoM Operational Security (OPSEC) advisor. Provides OPSEC methodology guidance, helps users understand operational risks, build secure operating habits, and accumulate experience through a case library. Does not execute commands directly; serves as decision support. Concrete technical specifications and OPSEC scoring are maintained in the iom-pentest skill. Trigger conditions: use when the user asks "is this safe?", "will this be detected?", "how should I think about OPSEC?", "risk assessment", "operational security advice", or "help me analyze the detection surface".
IoM OPSEC Advisor
Provides operational security methodology guidance. Does not duplicate concrete technical specifications (command usage, OPSEC scores, AV countermeasure matrices) — those are maintained centrally in the iom-pentest references. This skill focuses on mindset and decision frameworks.
Methodology: Five Questions Before Every Operation
Answer these five questions before executing any operation:
1. Do I know what is on the other side?
Do not execute any risky operation without first running enum av / ps. Operating blind is the number-one OPSEC killer.
2. What is the detection surface of this operation? Every operation has a detection surface. Understanding it is the prerequisite for assessing risk:
| Detection Dimension | Trigger Source | Monitored By |
|---|---|---|
| Process creation | New process, anomalous parent-child relationship | EDR, Sysmon Event 1 |
| Memory operations | Process injection, cross-process read/write | EDR kernel callbacks |
| File on disk | Files written to disk | AV real-time scanning |
| Registry | Run keys, service registration | Sysmon Event 12/13 |
| Network | Anomalous outbound traffic, lateral movement ports | NDR, firewall |
| Credential access | LSASS access | Credential Guard, EDR |
| Logging | ETW providers | SIEM, Defender ATP |
| API calls | Sensitive ntdll/kernel32 calls | EDR inline hooks |
3. Is there an alternative with a smaller detection surface?
Almost always yes. If your first instinct is logonpasswords, consider whether hashdump is sufficient.
4. What if it fails? Being blocked is not the same as being discovered, but retrying the same technique is self-exposure. Plan a fallback path.
5. Is this step actually necessary? If you can skip it, skip it. Every operation carries risk.
HITL Decision Framework
Triage user-requested operations by severity level:
Green Light (execute directly, inform the user)
- Read-only information gathering: sysinfo, whoami, ps, enum av
- Status checks: session, listener, pipeline list
- These operations have a minimal detection surface, but it is still worth telling the user what is happening
Yellow Light (present options, wait for confirmation)
- Operations with multiple implementation paths that differ significantly in OPSEC impact
- Privilege escalation, credential harvesting, persistence
- Present at least two options, annotating the detection surface of each
Red Light (strong warning, explicit confirmation required)
- Operations with an OPSEC score < 6
- Techniques known to be blocked by the current AV (per the case library)
- Operations that may destabilize the system (kernel exploits)
- Clearly state the risk, recommend alternatives, and wait for the user to explicitly confirm
Show full SKILL.md (207 more words)Show less
Case Library
The case library is the core of experience accumulation. Each case records the outcome of a specific operation in a specific environment, serving as a reference for future decisions.
Cases are stored in the reference/cases/ directory, named as <operation-type>-<security-product>.md.
See reference/case-template.md for the case format.
Using Cases
When a user requests an operation:
- Identify the security products in the target environment
- Search the case library for
<operation-type>-<security-product>.md - If a matching case exists, cite the historical conclusion and skip techniques known to fail
- If no matching case exists, assess per the methodology, execute, and record the result as a new case
Iteration Mechanism
Cases feed back into the iom-pentest references:
- A technique is consistently blocked by a specific AV — update the strategy matrix in
opsec-guide.md - A new safe execution path is discovered — update the corresponding phase reference in iom-pentest
- AV product behavior changes — update the security product identification table in
opsec-guide.md
This way the case library drives iterative improvement of the iom-pentest specifications, rather than maintaining duplicates in both places.
References
| Content | Location |
|---|---|
| Case template | reference/case-template.md |
| Case library | reference/cases/ |
| AV countermeasures and execution methods (detailed specs) | iom-pentest/reference/opsec-guide.md — Strategy Matrix, Execution Method Selection |
| Technique quick-reference and OPSEC scores | iom-pentest/reference/technique-reference.md — Credential Harvesting, UAC Bypass |
© chainreactors, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 2 other files in skills/iom-opsec of chainreactors/malice-network.
- SKILL.md
- reference/case-template.md
- reference/cases/cred-dump-defender.md
Open the folder on GitHubat commit 6c0e358
Compare with similar skills
Iom Opsec next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Iom Opsec this skillchainreactors/malice-network | 500 | — | ~1.4k | Automated safety check: Pass | Apache-2.0 | |
| Strix Code Vulnerability Scanusestrix/strix | 67k | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Code Audit3stoneBrother/code-audit | 893 | 1 repos | ~2.7k | Automated safety check: Pass | None | |
| Fix Strix Security Findingsusestrix/strix | 67k | — | ~1.5k | Automated safety check: Pass | Apache-2.0 | |
| Metabigor OSINT Reconj3ssie/metabigor | 1.9k | — | ~2.4k | Automated safety check: Pass | MIT | |
| Wooyun Legacytanweai/wooyun-legacy | 1.8k | — | ~1.9k | Automated safety check: Pass | Custom licence |
Similar skills
Code Audit
3stoneBrother/code-audit
Professional code security audit skill covering 55+ vulnerability types.
Fix Strix Security Findings
usestrix/strix
Triages findings from a Strix pentest by severity, fixes each root cause with a minimal change, and re-runs Strix to confirm the exploit no longer works.
Metabigor OSINT Recon
j3ssie/metabigor
Operates the metabigor CLI to map a target's network ranges, subdomains, ports, related domains, CDNs and archived URLs from free sources without API keys.
Wooyun Legacy
tanweai/wooyun-legacy
WooYun business logic vulnerability methodology — 22,132 real cases across 6 domains (authentication bypass, authorization bypass, payment tampering, information disclosure, logic flaws…
OWASP Top 10 Testing with Strix
usestrix/strix
Runs Strix's autonomous exploit agents against each OWASP Top 10:2025 category and the API Security Top 10, reporting only what could actually be proven with a proof-of-concept.
More from chainreactors/malice-network
Mal Develop
chainreactors/malice-network
MAL (Malice Scripting Language) plugin development guide. An agent skill from chainreactors/malice-network.
Related
Categories
Questions about Iom Opsec
What does Iom Opsec do?
IoM Operational Security (OPSEC) advisor. An agent skill from chainreactors/malice-network. Iom Opsec is an agent skill from chainreactors/malice-network. IoM Operational Security (OPSEC) advisor.
When should I use Iom Opsec?
Iom Opsec fits situations like: conditions: use when the user asks is this safe?; will this be detected?; how should I think about OPSEC?; risk assessment.
How do I install Iom Opsec in Claude Code?
Run `npx skills add chainreactors/malice-network --skill iom-opsec -a claude-code`. Or copy the skill folder (skills/iom-opsec in chainreactors/malice-network) into .claude/skills/iom-opsec in your project. Claude Code loads it when a task matches its description.
How do I install Iom Opsec in Codex?
Run `npx skills add chainreactors/malice-network --skill iom-opsec -a codex`. Or copy the skill folder (skills/iom-opsec in chainreactors/malice-network) into .agents/skills/iom-opsec in your project. Codex loads it when a task matches its description.
Can I use Iom Opsec in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add chainreactors/malice-network --skill iom-opsec -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/iom-opsec, .gemini/skills/iom-opsec, .github/skills/iom-opsec and .opencode/skills/iom-opsec in your project.
What does Iom Opsec need to run?
SKILL.md names no scripts, command-line tools or credentials: Iom Opsec is instructions for the agent only.
Does Iom Opsec access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Iom Opsec safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Iom Opsec use?
Iom Opsec is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Iom Opsec use?
About 1.4k tokens (SKILL.md is roughly 5.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Iom Opsec?
Skills that share tags, products or a category with Iom Opsec: Strix Code Vulnerability Scan (usestrix/strix, 67k stars), Code Audit (3stoneBrother/code-audit, 893 stars), Fix Strix Security Findings (usestrix/strix, 67k stars) and Metabigor OSINT Recon (j3ssie/metabigor, 1.9k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Iom Opsec?
chainreactors (a GitHub organization) maintains it in chainreactors/malice-network, which has 500 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on September 5, 2026.
Source: chainreactors/malice-network on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.