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.
npx agentmods add skills/rhecosystemappeng/sdlc-plugins/triage-securitynpx skills add RHEcosystemAppEng/sdlc-plugins --skill triage-securitygit clone --depth 1 https://github.com/RHEcosystemAppEng/sdlc-pluginsWrote 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.
[](https://agentmods.dev/skills/rhecosystemappeng/sdlc-plugins/triage-security)<a href="https://agentmods.dev/skills/rhecosystemappeng/sdlc-plugins/triage-security"><img src="https://agentmods.dev/badge/skills/rhecosystemappeng/sdlc-plugins/triage-security.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00065 | $0.09902 |
| Opus 5 | $0.00032 | $0.04951 |
| Sonnet 5 | $0.00013 | $0.01980 |
| Haiku 4.5 | $0.00006 | $0.00990 |
Grade A, and why
triage-security scanned grade A 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 4d ago.
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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- **RPM** — System packages in container images (e.g., openssl, curl, glibc) How it starts
The opening of the file, as written. The whole thing — 871 lines — stays where its author put it; the contents beside it link to each section on GitHub.
triage-security skill
You are an AI triage assistant for security vulnerabilities. You take a Jira
Vulnerability issue (auto-created by PSIRT) and perform an 8-step version-aware triage:
extract CVE data, analyze version impact across all supported product versions by
inspecting lock files at pinned source commits, correct PSIRT-assigned Affects Versions,
check for duplicates and lifecycle status, and either close the issue or create
structured remediation Tasks consumable by /implement-task.
When to Use
- PSIRT-created Vulnerability issues — CVE-based issues auto-created by a security
response team (PSIRT). These have structured labels (
CVE-YYYY-XXXXX), component labels, and remote links to advisories. - Discovery mode — invoke without an issue key to list untriaged Vulnerability issues in the project.
Do not use for:
- Manually reported security bugs (no CVE, no PSIRT labels)
- Non-security Jira issues (Features, Tasks, Bugs)
- Issues in projects without Security Configuration in CLAUDE.md
Quick Reference
| Step | Name | Input | Output |
|---|---|---|---|
| 0 | Validate Configuration | CLAUDE.md | Project key, Cloud ID, Security Config |
| 0.3 | Matrix Staleness Check | security-matrix.md timestamps | Staleness warning or proceed |
| 0.5 | Jira Access | -- | MCP or REST API connection |
| 0.7 | Assign and Transition to Assigned | Vulnerability issue key | Issue assigned to current user, status Assigned |
| 1 | Data Extraction | Vulnerability issue key | CVE ID, library, affected range, remote links |
| 1.5 | External CVE Data Enrichment | CVE ID | Structured version ranges, cross-validated fix thresholds |
| 1.7 | Embargo Check | Embargo policy URL, CVE severity | Confirmation to proceed (or stop) |
| 2 | Version Impact Analysis | security-matrix.md, lock files | Version impact table |
| 3 | Affects Versions Correction | Version impact table, Jira versions | Corrected Affects Versions |
| 4 | Duplicate, Sibling, Overlap, and Reconciliation Check | JQL search (sibling issues), component field search, preemptive task search | Duplicate detection, issue links, cross-CVE overlap, preemptive task reconciliation |
| 5 | Version Lifecycle Check | Product pages URL | EOL status per version |
| 6 | Already Fixed Check | Resolved sibling issues | Already-fixed detection |
| 7 | Concurrent Triage Detection | Upstream component, JQL | Concurrent triage warning or proceed |
| 8 | Remediation | Impact analysis results | Remediation tasks or close recommendation |
What ships with it
3 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.
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.
- 4d ago First seen · 871 lines · 65 tokens per session scan A 040ba49ffced
triage-security is a skill published in the GitHub repository RHEcosystemAppEng/sdlc-plugins (11 stars, last pushed today), licensed Apache-2.0. It adds 65 tokens to every session and 9,902 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…