Agent skill

Triage

by hashgraph-online in hashgraph-online/awesome-codex-plugins

Adversarial validation of vulnerability findings. An agent skill from hashgraph-online/awesome-codex-plugins.

Apache-2.0Auto-check passed

Install Triage

skills CLI

$ npx skills add hashgraph-online/awesome-codex-plugins --skill triage -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install hashgraph-online/awesome-codex-plugins triage --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/hashgraph-online/awesome-codex-plugins.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/epicsagas/epic-harness/skills/triage .claude/skills/triage && rm -rf skills-src

Use ~/.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/

Paste into Claude Code

Install the "triage" agent skill from https://github.com/hashgraph-online/awesome-codex-plugins/tree/main/plugins/epicsagas/epic-harness/skills/triage into .claude/skills/triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "triage", 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

$skill-installer install https://github.com/hashgraph-online/awesome-codex-plugins/tree/main/plugins/epicsagas/epic-harness/skills/triage

Type 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.

skills CLI

$ npx skills add hashgraph-online/awesome-codex-plugins --skill triage -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install hashgraph-online/awesome-codex-plugins triage --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/hashgraph-online/awesome-codex-plugins.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/epicsagas/epic-harness/skills/triage .agents/skills/triage && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "triage" agent skill from https://github.com/hashgraph-online/awesome-codex-plugins/tree/main/plugins/epicsagas/epic-harness/skills/triage into .agents/skills/triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "triage", 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.

skills CLI

$ npx skills add hashgraph-online/awesome-codex-plugins --skill triage -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install hashgraph-online/awesome-codex-plugins triage --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/hashgraph-online/awesome-codex-plugins.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/epicsagas/epic-harness/skills/triage .cursor/skills/triage && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "triage" agent skill from https://github.com/hashgraph-online/awesome-codex-plugins/tree/main/plugins/epicsagas/epic-harness/skills/triage into .cursor/skills/triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "triage", 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

$ gemini skills install https://github.com/hashgraph-online/awesome-codex-plugins.git --path plugins/epicsagas/epic-harness/skills/triage

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add hashgraph-online/awesome-codex-plugins --skill triage -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install hashgraph-online/awesome-codex-plugins triage --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/hashgraph-online/awesome-codex-plugins.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/epicsagas/epic-harness/skills/triage .gemini/skills/triage && rm -rf skills-src

Use ~/.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/

Paste into Gemini CLI

Install the "triage" agent skill from https://github.com/hashgraph-online/awesome-codex-plugins/tree/main/plugins/epicsagas/epic-harness/skills/triage into .gemini/skills/triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "triage", 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.

GitHub CLI

$ gh skill install hashgraph-online/awesome-codex-plugins triage

Installs 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).

skills CLI

$ npx skills add hashgraph-online/awesome-codex-plugins --skill triage -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/hashgraph-online/awesome-codex-plugins.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/epicsagas/epic-harness/skills/triage .github/skills/triage && rm -rf skills-src

Use ~/.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/

Paste into GitHub Copilot

Install the "triage" agent skill from https://github.com/hashgraph-online/awesome-codex-plugins/tree/main/plugins/epicsagas/epic-harness/skills/triage into .github/skills/triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "triage", 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.

skills CLI

$ npx skills add hashgraph-online/awesome-codex-plugins --skill triage -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install hashgraph-online/awesome-codex-plugins triage --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/hashgraph-online/awesome-codex-plugins.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/epicsagas/epic-harness/skills/triage .opencode/skills/triage && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "triage" agent skill from https://github.com/hashgraph-online/awesome-codex-plugins/tree/main/plugins/epicsagas/epic-harness/skills/triage into .opencode/skills/triage/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "triage", 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: triage
GitHub stars: 1.3k
Token cost: ~1.5k tokens
SKILL.md length: 486 words
Files: 1
Skills in repo: 714
Repo updated: Oct 9, 2026
First seen: Oct 7, 2026
Licence: Apache-2.0

At a glance

Adversarial validation of vulnerability findings. An agent skill from hashgraph-online/awesome-codex-plugins.

Works in 5 steps: Load Inputs → Adversarial Review → Dependency Analysis → …
Triaging security findings
SKILL.md covers Iron Law, Process, Anti-Rationalization and Evidence Required, plus 1 more section
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Triage is an agent skill from hashgraph-online/awesome-codex-plugins. Adversarial validation of vulnerability findings. Use when triaging security findings, validating vulnerabilities, or prioritizing remediation.

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: A curated list of awesome OpenAI Codex / ChatGPT plugins, skills, and resources. The 1 Codex Marketplace. See live plugins at: https://hol.org/plugins/best-codex-plugins. The licence is Apache-2.0.

When your agent uses it

Triaging security findings
Validating vulnerabilities
Prioritizing remediation

Example prompts

“/triage”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

Load Inputs
Adversarial Review
Dependency Analysis
Produce Output
Report

What it can do on your machine

Read from SKILL.md and the folder at commit 9e7b281. 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 (its code samples are json).
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

Triage loads about 1.5k tokens when it runs. Until then it costs about 38 tokens; SKILL.md has 486 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~38
When it runs · the whole SKILL.md, loaded when a task matches: ~1.5k

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 hashgraph-online/awesome-codex-plugins at commit 9e7b281, republished under its Apache-2.0 licence (© hashgraph-online). 486 words, ~1,510 tokens.

Download SKILL.mdSave it as .claude/skills/triage/SKILL.md (or your agent's skills folder).

name: triage
description: Adversarial validation of vulnerability findings. Use when triaging security findings, validating vulnerabilities, or prioritizing remediation.

Triage — Adversarial Vulnerability Validation

Iron Law

A vulnerability finding is not confirmed until an adversary would agree it's exploitable. Unvalidated findings are noise.

Process

Step 0: Load Inputs

Required inputs (in order of preference):

VULN-FINDINGS.json from /vuln-scan
Raw findings from /audit --security
User-provided finding list

Optional:

THREAT_MODEL.md for threat scenario context
.harness/engagement.md for scope constraints

If no findings input exists, suggest: "Run /vuln-scan first to generate findings to triage."

Step 1: Adversarial Review

For each finding, challenge it from an attacker's perspective:

Exploitability Check

Can input reach the vulnerable code? Trace the data flow from entry point to vulnerability.
Can the attacker control the input? Distinguish between user-controlled vs. system-generated data.
Is there a path to impact? Connecting the vulnerability to a security consequence (data leak, code exec, DoS).
Are there bypasses for existing mitigations? WAF, input validation, CSP — all have bypass techniques.

Severity Validation

Criteria	Adjust
Requires authentication	Lower by 1 level
Requires specific permissions	Lower by 1 level
Chained with another finding	Raise by 1 level
Affects all users	Raise by 1 level
No mitigation in place	Raise by 1 level
Defense-in-depth exists	Lower by 1 level

Classification

Class	Meaning
`CONFIRMED`	Exploitable with demonstrated path
`LIKELY`	Exploitable with high confidence, minor gaps in proof
`POSSIBLE`	Theoretical, needs more investigation
`FALSE_POSITIVE`	Not exploitable with justification
`ACCEPTED_RISK`	Known, documented, accepted by team

Step 2: Dependency Analysis

Check if findings chain together:

Find pairs where finding A enables finding B (e.g., IDOR → data exposure)
Mark chains — chained findings are more severe than individual findings
Identify root causes — multiple findings from the same root cause should be grouped

Step 3: Produce Output

Write TRIAGE.json:

json

{
  "triage_date": "ISO-8601",
  "source": "VULN-FINDINGS.json | audit | manual",
  "findings": [
    {
      "id": "V1",
      "classification": "CONFIRMED | LIKELY | POSSIBLE | FALSE_POSITIVE | ACCEPTED_RISK",
      "original_severity": "CRITICAL",
      "adjusted_severity": "HIGH",
      "severity_adjustments": ["requires auth (-1)", "no mitigation (+1)"],
      "exploit_path": ["entry point → vulnerable function → impact"],
      "chains_with": ["V3"],
      "root_cause_group": "RC1",
      "remediation": "specific fix instruction",
      "effort": "low | medium | high",
      "validation_notes": "why this classification was chosen"
    }
  ],
  "root_cause_groups": [
    {
      "id": "RC1",
      "description": "shared root cause",
      "findings": ["V1", "V2"],
      "fix_once": "single fix that resolves all findings in group"
    }
  ],
  "chains": [
    {
      "findings": ["V1", "V3"],
      "combined_severity": "CRITICAL",
      "description": "V1 enables V3, creating..."
    }
  ],
  "summary": {
    "total_input": 10,
    "confirmed": 3,
    "likely": 2,
    "possible": 1,
    "false_positive": 2,
    "accepted_risk": 2,
    "root_cause_groups": 3,
    "chains": 1
  },
  "action_items": [
    {
      "priority": 1,
      "severity": "CRITICAL",
      "finding_ids": ["V1"],
      "action": "specific remediation step",
      "effort": "low"
    }
  ]
}

Step 4: Report

Present prioritized remediation plan:

## Triage Report

### Summary
- Input: N findings
- Confirmed: X | Likely: Y | False positives: Z
- Root cause groups: K (fix-once opportunities)
- Chained findings: C

### Priority Actions
1. [CRITICAL] V1: {description} — {effort} effort
   Fix: {remediation}
2. [HIGH] V2+V3 (chain): {description} — {effort} effort
   Fix: {remediation}

### Accepted Risks
- V7: {description} — {justification}

### Suggested Next Steps
- Fix priority 1-3 before merge
- Run `/vuln-scan` after fixes to verify

Show full SKILL.md (197 more words)Show less

Anti-Rationalization

Excuse	Rebuttal	What to do instead
"All findings are real, no need to triage"	False positives waste fix time and erode trust in the process.	Validate every finding. Noise reduces signal.
"Triaging takes too long"	Fixing false positives takes longer than triaging them.	Triage first, fix only confirmed findings.
"It's obviously a vulnerability"	"Obvious" vulnerabilities are often mitigated by context you haven't checked.	Trace the exploit path before confirming.
"We can just fix them all"	Not all findings need fixing. Some are accepted risks.	Prioritize by confirmed severity and effort.
"Chaining is theoretical"	Real-world breaches use chained vulnerabilities.	Check for chains — they change severity.

Evidence Required

Every finding classified (CONFIRMED/LIKELY/POSSIBLE/FALSE_POSITIVE/ACCEPTED_RISK)
Each CONFIRMED finding has a traced exploit path
Each FALSE_POSITIVE has justification for dismissal
Severity adjustments documented per finding
Root cause groups identified where applicable
Chained findings identified and combined severity assessed
TRIAGE.json written with action items
Priority actions ordered by severity × effort

Red Flags

All findings marked CONFIRMED without exploit paths
All findings marked FALSE_POSITIVE without justification
No severity adjustments — original severity is almost never perfect
Ignoring finding chains — individual severity ≠ chain severity
Skipping dependency analysis between findings
TRIAGE.json action items not ordered by priority

Files

Just SKILL.md in plugins/epicsagas/epic-harness/skills/triage of hashgraph-online/awesome-codex-plugins.

Open the folder on GitHubat commit 9e7b281

Compare with similar skills

Triage 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.

Triage compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Triage this skillhashgraph-online/awesome-codex-plugins	1.3k	—	~1.5k	Automated safety check: Pass	Apache-2.0	yesterday
Warp Vulnerability Triagewarpdotdev/warp	65k	1 repos	~2.1k	Automated safety check: Pass	AGPL-3.0	today
Triage Validationsickn33/agentic-awesome-skills	47k	1 repos	~6.1k	Automated safety check: Pass	MIT	today
Performing Web Application Vulnerability Triagemukul975/Anthropic-Cybersecurity-Skills	34k	—	~2.2k	Automated safety check: Pass	Apache-2.0	1 mo ago
Triaging Vulnerabilities With Ssvc Frameworkmukul975/Anthropic-Cybersecurity-Skills	34k	—	~1.9k	Automated safety check: Pass	Apache-2.0	1 mo ago
Bug Bounty Triage Validationawarexone/Agentic-Bug-Hunter	5.3k	3 repos	~3.4k	Automated safety check: Pass	MIT	yesterday

Similar skills

Warp Vulnerability Triage
warpdotdev/warp
Gathers security findings from Dependabot, GCP container scanning, Docker Scout and Linear security issues, then triages and remediates them across Warp's repos and images.
65k GitHub starsUsed in 1 repo~2.1k tokens
SecurityAuto-check passed
Triage Validation
sickn33/agentic-awesome-skills
Finding validation before writing any report. An agent skill from sickn33/agentic-awesome-skills.
47k GitHub starsUsed in 1 repo~6.1k tokens
SecurityAuto-check passed
Performing Web Application Vulnerability Triage
mukul975/Anthropic-Cybersecurity-Skills
Triages web application vulnerability findings from DAST/SAST scanners such as Burp Suite and ZAP, using the OWASP Risk Rating Methodology to confirm true positives, dismiss false positives, and…
34k GitHub stars~2.2k tokensUpdated 1 mo ago
SecurityAuto-check passed
Triaging Vulnerabilities With Ssvc Framework
mukul975/Anthropic-Cybersecurity-Skills
Triages and prioritizes vulnerabilities with CISA's Stakeholder-Specific Vulnerability Categorization (SSVC) decision tree, weighing exploitation status (via the CISA KEV catalog and FIRST EPSS…
34k GitHub stars~1.9k tokensUpdated 1 mo ago
SecurityAuto-check passed
Bug Bounty Triage Validation
awarexone/Agentic-Bug-Hunter
Screens a vulnerability finding with a seven-question gate and pre-submission checks before any report is written, so weak or out-of-scope findings are dropped early.
5.3k GitHub starsUsed in 3 repos~3.4k tokens
SecurityAuto-check passed
Vulnerability Triage Brocards
trailofbits/skills
Official
Screens vulnerability reports, CVEs and automated findings against seven rules of thumb to accept, dismiss or ask for more information before any deep analysis.
7.4k GitHub stars~2.2k tokensUpdated 2 days ago
SecurityAuto-check passed

More from hashgraph-online/awesome-codex-plugins

All 714 skills in this repo

Anime Reaction Gif
hashgraph-online/awesome-codex-plugins
Create original anime-style reaction stickers as looping GIFs and MP4 previews, using generated character pose sheets and timed key poses.
1.3k GitHub stars~922 tokensUpdated yesterday
Auto-check passed
Calibredb
hashgraph-online/awesome-codex-plugins
Manage and query Calibre libraries with the calibredb CLI (local paths or Calibre Content server URLs).
1.3k GitHub stars~1k tokensUpdated yesterday
Auto-check passed
Rust API Test Harness
hashgraph-online/awesome-codex-plugins
A skill your agent uses when adding, changing, testing, or debugging Rust HTTP APIs and services, especially when Codex needs black-box integration tests, random-port app startup, real database test…
1.3k GitHub stars~1.7k tokensUpdated yesterday
Auto-check passed
Art
hashgraph-online/awesome-codex-plugins
Make a studio's game look like something at build time — a cover from a real frame of the game (free), painted covers, backdrops, textures and character plates from image models through the…
1.3k GitHub stars~2.4k tokensUpdated yesterday
Auto-check passed
Calle
hashgraph-online/awesome-codex-plugins
Use CALL-E from Codex through the calle CLI. An agent skill from hashgraph-online/awesome-codex-plugins.
1.3k GitHub stars~2.9k tokensUpdated yesterday
Auto-check passed
Game Balance Economy
hashgraph-online/awesome-codex-plugins
Balance game difficulty, resources, rewards, probability, progression, economies, and dominant strategies.
1.3k GitHub stars~618 tokensUpdated yesterday
Auto-check passed

Questions about Triage

What does Triage do?

Adversarial validation of vulnerability findings. An agent skill from hashgraph-online/awesome-codex-plugins. Triage is an agent skill from hashgraph-online/awesome-codex-plugins. Adversarial validation of vulnerability findings.

When should I use Triage?

Triage fits situations like: triaging security findings; validating vulnerabilities; prioritizing remediation.

How do I install Triage in Claude Code?

Run `npx skills add hashgraph-online/awesome-codex-plugins --skill triage -a claude-code`. Or copy the skill folder (plugins/epicsagas/epic-harness/skills/triage in hashgraph-online/awesome-codex-plugins) into .claude/skills/triage in your project. Claude Code loads it when a task matches its description.

How do I install Triage in Codex?

Run `npx skills add hashgraph-online/awesome-codex-plugins --skill triage -a codex`. Or copy the skill folder (plugins/epicsagas/epic-harness/skills/triage in hashgraph-online/awesome-codex-plugins) into .agents/skills/triage in your project. Codex loads it when a task matches its description.

Can I use Triage 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 hashgraph-online/awesome-codex-plugins --skill triage -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/triage, .gemini/skills/triage, .github/skills/triage and .opencode/skills/triage in your project.

What does Triage need to run?

SKILL.md names no scripts, command-line tools or credentials: Triage is instructions for the agent only.

Does Triage 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 Triage 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 Triage use?

Triage 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 Triage use?

About 1.5k tokens (SKILL.md is roughly 6k 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 Triage?

Skills that share tags, products or a category with Triage: Warp Vulnerability Triage (warpdotdev/warp, 65k stars), Triage Validation (sickn33/agentic-awesome-skills, 47k stars), Performing Web Application Vulnerability Triage (mukul975/Anthropic-Cybersecurity-Skills, 34k stars) and Triaging Vulnerabilities With Ssvc Framework (mukul975/Anthropic-Cybersecurity-Skills, 34k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Triage?

hashgraph-online (a GitHub organization) maintains it in hashgraph-online/awesome-codex-plugins, which has 1,255 GitHub stars. The repository holds 714 skills in this directory. The repository was last updated on October 9, 2026.

Source: hashgraph-online/awesome-codex-plugins on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Triage

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Triage — Adversarial Vulnerability Validation

Iron Law

Process

Step 0: Load Inputs

Step 1: Adversarial Review

Exploitability Check

Severity Validation

Classification

Step 2: Dependency Analysis

Step 3: Produce Output

Step 4: Report

Anti-Rationalization

Evidence Required

Red Flags

Files

Compare with similar skills

Similar skills

More from hashgraph-online/awesome-codex-plugins

Questions about Triage