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/dmc5179/redhat-security-data-api-mcp/redhat-security-datanpx skills add dmc5179/redhat-security-data-api-mcp --skill redhat-security-datagit clone --depth 1 https://github.com/dmc5179/redhat-security-data-api-mcpWrote 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/dmc5179/redhat-security-data-api-mcp/redhat-security-data)<a href="https://agentmods.dev/skills/dmc5179/redhat-security-data-api-mcp/redhat-security-data"><img src="https://agentmods.dev/badge/skills/dmc5179/redhat-security-data-api-mcp/redhat-security-data.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.00044 | $0.01322 |
| Opus 5 | $0.00022 | $0.00661 |
| Sonnet 5 | $0.00009 | $0.00264 |
| Haiku 4.5 | $0.00004 | $0.00132 |
Grade A, and why
redhat-security-data scanned grade A with 0 findings 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 3d 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.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Red Hat Security Data
Use the Red Hat Security Data API MCP server to investigate CVEs, CSAF advisories, and OVAL streams. This skill teaches you when and how to chain the six MCP tools for common security questions.
MCP Tools Available
| Tool | Use when |
|---|---|
search_cves |
Finding CVEs by date range, severity, CVSS score, package, product, CWE, or advisory |
get_cve_details |
Getting full details for a specific CVE (severity, CVSS, affected releases, package state, mitigation) |
search_csaf |
Finding CSAF advisories by date, severity, CVE, package, Bugzilla ID, or RHSA ID |
get_csaf_details |
Getting the full CSAF/VEX document for a specific RHSA advisory |
list_oval_streams |
Listing available OVAL v2 data streams by product label or date |
get_oval_stream |
Getting OVAL definitions for a specific product (e.g. RHEL7, RHEL9) |
Investigation Patterns
Pattern 1: "Is product X affected by CVE-YYYY-NNNNN?"
get_cve_detailswith the CVE ID- Check
package_statefor the product — look for "Not affected", "Will not fix", "Fix deferred", or "Affected" - Check
affected_releasefor errata that fix the CVE on that product - If an errata exists, use
get_csaf_detailswith the RHSA ID to get the full advisory including exact fixed versions
Pattern 2: "What critical CVEs were published this week?"
search_cveswithseverity=criticalandcreated_days_ago=7- For each CVE of interest,
get_cve_detailsto get full impact details - If the user cares about a specific product, filter results by checking
affected_releaseandpackage_state
Pattern 3: "What advisories fix CVE-YYYY-NNNNN?"
get_cve_detailsto get the list ofaffected_releaseentries with their advisory linkssearch_csafwithcve=CVE-YYYY-NNNNNto find all CSAF advisories that reference the CVEget_csaf_detailsfor specific advisories to get the product tree, fixed package versions, and remediation guidance
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.
- 3d ago First seen · 108 lines · 44 tokens per session scan A e75ae4ebbdef
redhat-security-data is a skill published in the GitHub repository dmc5179/redhat-security-data-api-mcp (0 stars, last pushed 15d ago), licensed Apache-2.0. It adds 44 tokens to every session and 1,322 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
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…