What is redhat-security-data?

A guide for investigating Red Hat security data through an MCP server. It explains how to use six tools for CVEs, CSAF advisories, and OVAL data streams, including multi-step investigations.

Searching CVEs and advisories, retrieving detailed vulnerability records, checking whether products are affected, and obtaining OVAL data for products such as RHEL 7 or RHEL 9.

It helps an agent choose the right security query and combine results to answer questions about vulnerabilities and affected Red Hat products.

redhat-security-data — Skill for Claude Code and Codex by dmc5179

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.

Any agent

npx skills add dmc5179/redhat-security-data-api-mcp --skill redhat-security-data

Clone the repo

git clone --depth 1 https://github.com/dmc5179/redhat-security-data-api-mcp

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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/dmc5179/redhat-security-data-api-mcp/redhat-security-data/github.svg)](https://agentmods.dev/skills/dmc5179/redhat-security-data-api-mcp/redhat-security-data)

Your own site

<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/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<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="Reviewed on agentmods" width="80" height="20"></a>

Per session 44 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,322 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.

Model	Per session	Once invoked
Fable 5.1	$0.00044	$0.01322
Opus 5.5	$0.00018	$0.00529
Sonnet 5.5	$0.00009	$0.00264
Haiku 4.5	$0.00004	$0.00132

Measured 1mo ago against content hash e75ae4ebbdef, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 1mo 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.

skills/redhat-security-data/SKILL.md · 108 lines

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_details with the CVE ID
Check package_state for the product — look for "Not affected", "Will not fix", "Fix deferred", or "Affected"
Check affected_release for errata that fix the CVE on that product
If an errata exists, use get_csaf_details with the RHSA ID to get the full advisory including exact fixed versions

Pattern 2: "What critical CVEs were published this week?"

search_cves with severity=critical and created_days_ago=7
For each CVE of interest, get_cve_details to get full impact details
If the user cares about a specific product, filter results by checking affected_release and package_state

Pattern 3: "What advisories fix CVE-YYYY-NNNNN?"

get_cve_details to get the list of affected_release entries with their advisory links
search_csaf with cve=CVE-YYYY-NNNNN to find all CSAF advisories that reference the CVE
get_csaf_details for specific advisories to get the product tree, fixed package versions, and remediation guidance

Read the full file on GitHub · 108 lines

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.

1mo ago First seen · 108 lines · 44 tokens per session scan A e75ae4ebbdef

Subscribe to this mod's changes

redhat-security-data is a skill published in the GitHub repository dmc5179/redhat-security-data-api-mcp (0 stars, last pushed 2mo 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.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.

Research Security

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

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.

microsoft/vscode · 53 tokens

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…

microsoft/vscode · 71 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens