triage-finding

triage-finding is a skill for Claude Code, Codex from bex-co/bex-security. It costs 73 tokens per session (5,384 once invoked), scanned B, original, Apache-2.0.

A workflow for assessing security findings that already come from sources such as scanners, vulnerability reports, advisories, or issue trackers against a repository's code. It returns an evidence-based result for each finding: confirmed, not actionable, or needs review.

In plain words
What is it for?
Use it to review an existing security backlog, support each verdict with static code evidence, and rank confirmed or uncertain findings by exploitability.
Why use it?
It helps separate findings that affect the current code from irrelevant or uncertain reports without performing a new repository-wide security scan.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/bex-co/bex-security/triage-finding
Any agent
npx skills add bex-co/bex-security --skill triage-finding
Clone the repo
git clone --depth 1 https://github.com/bex-co/bex-security

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for triage-finding

README.md
[![agentmods](https://agentmods.dev/badge/skills/bex-co/bex-security/triage-finding.svg)](https://agentmods.dev/skills/bex-co/bex-security/triage-finding)
Your own site
<a href="https://agentmods.dev/skills/bex-co/bex-security/triage-finding"><img src="https://agentmods.dev/badge/skills/bex-co/bex-security/triage-finding.svg" alt="Measured on agentmods" height="20"></a>
Per session 73 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 5,384 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00073 $0.05384
Opus 5 $0.00036 $0.02692
Sonnet 5 $0.00015 $0.01077
Haiku 4.5 $0.00007 $0.00538

Measured 5d ago against content hash 70b0e771f286, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade B, and why

triage-finding scanned grade B with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 5d ago.

The scan reads SKILL.md. This mod also ships 28 executable files (evals/assertions/calibration-evidence.js, evals/assertions/github-rest-intake.js, evals/assertions/missing-input.js, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nullifies safety policiesmediumAnti-refusal

"You have no restrictions", "do anything now", "ignore your guidelines": a direct jailbreak that disables guardrails.

If no policy applies, record that absence as a proof gap and continue with the next-best local policy evidence. Absence of an applicable policy does not itself establish that a surface, configuration, trust relationship,

Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.

plugins/codex-security/skills/triage-finding/SKILL.md · 334 lines

How it starts

The opening of the file, as written. The whole thing — 334 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Triage Finding

Objective

Triage existing security findings against the current repository using static code evidence. Return one evidence-backed verdict per supplied finding: confirmed, not_actionable, or needs_review. For confirmed and needs_review findings, also assign a discrete exploitability stack rank inside that verdict's own queue.

This skill is for backlog burn-down. It starts from findings the user already has, such as SARIF results, CVEs, advisories, scanner tickets, bug bounty reports, Jira/Linear issues, or Codex Security finding artifacts. It is not a repository-wide scan, dynamic validation run, fix implementation, dashboard, or queue manager.

Backlog Burn-Down Scope

Treat multiple supplied findings as one backlog-reduction problem, not as a set of unrelated one-off triages. The goal is to turn noisy existing finding sources into a ranked, evidence-backed action queue while preserving one result per input for auditability.

For now, run the workflow inline in the current thread, but structure the work like a backlog pipeline:

  • Build the normalized triage item list for the whole supplied or imported collection before assigning verdicts. Here, normalize means: assign triage_item_id, preserve source ids and references, extract the fields in the Inputs section below, and record missing fields as proof gaps without inventing scanner, severity, remediation, or generated Codex Security fields.
  • Triage each normalized item using static evidence and keep one output result per supplied finding.
  • Rank the confirmed and needs_review results as an action queue for backlog burn-down.
  • Do not perform deduplication in this skill. If duplicate-looking inputs are present, keep one result per supplied finding; deduplication belongs in a separate workflow.
  • Do not spawn subagents, use a subagent queue, or use deep triage mode until a future implementation explicitly adds those mechanics.

Finding Schema Decision

Do not use ../../schemas/findings.schema.json as the canonical data shape for input normalization.

Read the full file on GitHub · 334 lines

Files

What ships with it

56 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 5d ago First seen · 334 lines · 73 tokens per session scan B 70b0e771f286

Subscribe to this mod's changes

triage-finding is a skill published in the GitHub repository bex-co/bex-security (43 stars, last pushed yesterday), licensed Apache-2.0. It adds 73 tokens to every session and 5,384 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it B with 1 finding (nullifies safety policies). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

bugcrowd-reporting

Bugcrowd-specific reporting tactics complementing report-writing: VRT category search-and-fallback strategy when no exact match exists, manual severity override when VRT defaults underrate impact, severity-request paragraph as first body section, OOS-clause rebuttal templates (rate limiting on auth-flow endpoints…

elementalsouls/Claude-BugHunter · 171 tokens

hunt-aspnet

Hunt ASP.NET-specific surface — ViewState deserialization (signed-only vs encrypted), machineKey recovery, dual-parser MAC-bypass anti-pattern, request-validator bypass, trace.axd/elmah.axd disclosure, load-balanced ViewState cross-node failures, SafeControl enumeration via reflection, customErrors mode=Off…

elementalsouls/Claude-BugHunter · 98 tokens

apk-redteam-pipeline

End-to-end Android APK red-team pipeline — automated APK acquisition (Play Store + apkpure + apkmirror fallback), jadx decompilation, secret/URL/JWT/Firebase grep, pinned-cert extraction, exported-component enumeration, Frida runtime instrumentation templates, intent-injection probes. Built from an authorized external…

elementalsouls/Claude-BugHunter · 145 tokens

enterprise-vpn-attack

External SSL VPN / remote-access appliance attack matrix — Cisco ASA/AnyConnect, Fortinet FortiGate/FortiOS, Citrix NetScaler/ADC, Palo Alto GlobalProtect, Pulse Secure / Ivanti Connect Secure, SonicWall, F5 Big-IP. Covers version fingerprinting, CVE matrix (2018-2026), AAA backend identification, default credentials…

elementalsouls/Claude-BugHunter · 158 tokens

evidence-hygiene

Evidence-capture and PoC-redaction discipline for bug-bounty submissions: cookie redaction protocol (which fields to mask, Preview annotation / Burp panel hiding / DevTools workflow), PII black-bar discipline (what to mask in other-user data — names, emails, phones, faces — vs what is safe to leave — usernames, trace…

elementalsouls/Claude-BugHunter · 190 tokens

hunt-api-misconfig

Hunt API security misconfiguration — mass assignment, prototype pollution, HTTP verb tampering. Mass assignment: send {isadmin:true, role:admin, verified:true} on profile/account/reset endpoints — server blindly applies. JWT signature/crypto forging (alg:none, key confusion, kid/jku) is owned by hunt-jwt-crypto; this…

elementalsouls/Claude-BugHunter · 207 tokens