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/redhatinsights/insights-mcp/getting-startednpx skills add RedHatInsights/insights-mcp --skill getting-startedgit clone --depth 1 https://github.com/RedHatInsights/insights-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/redhatinsights/insights-mcp/getting-started)<a href="https://agentmods.dev/skills/redhatinsights/insights-mcp/getting-started"><img src="https://agentmods.dev/badge/skills/redhatinsights/insights-mcp/getting-started.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.1 | $0.00106 | $0.01685 |
| Opus 5 | $0.00053 | $0.00843 |
| Sonnet 5 | $0.00021 | $0.00337 |
| Haiku 4.5 | $0.00011 | $0.00169 |
Grade A, and why
getting-started 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 6d 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 — 160 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Getting Started with Red Hat Lightspeed MCP
Guide the user from zero to a working MCP connection. Adapt the steps below to their situation — ask which MCP client they use and whether they already have a Red Hat service account before walking through everything.
Install Skills with Lola (optional)
If the user wants the Lightspeed MCP skills installed into their AI assistant without cloning the full repo, they can use Lola — a universal AI Context Package Manager.
# Install Lola (one-time)
uv tool install git+https://github.com/RedHatProductSecurity/lola
# Add the Lightspeed marketplace (one-time)
lola market add lightspeed https://raw.githubusercontent.com/RedHatInsights/insights-mcp/main/lola-marketplace.yml
# Install skills to your AI assistant
lola install rh-lightspeed-mcp-skills -a cursor
lola install rh-lightspeed-mcp-skills -a claude-code
lola install rh-lightspeed-mcp-skills -a gemini-cli
This installs the skills to the assistant's native directory (e.g.,
.cursor/skills/, .claude/skills/). Users who clone the repo already have
the skills in .agents/skills/ — Lola is for distribution without cloning.
Setup Flow
1. Prerequisites
The user needs:
podmanordockerinstalled- A Red Hat account at https://console.redhat.com
- An MCP-compatible client
On macOS, if podman is installed but the client can't find it, use the full
path from which podman (usually /opt/homebrew/bin/podman or
/usr/local/bin/podman).
2. Authentication
THIS STEP MUST BE PERFORMED BY THE USER — NOT BY THE AGENT. Do not attempt to create, modify, or manage service accounts or permissions on behalf of the user. Only provide instructions and let the user act.
The user needs a Red Hat service account. Direct them to do the following:
- Go to https://console.redhat.com → Settings (gear icon) → "Service Accounts"
- Create a service account → save the Client ID and Client Secret
- Provide those values as
LIGHTSPEED_CLIENT_IDandLIGHTSPEED_CLIENT_SECRET
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.
- 6d ago First seen · 160 lines · 106 tokens per session scan A eba210e707df
getting-started is a skill published in the GitHub repository RedHatInsights/insights-mcp (24 stars, last pushed yesterday), licensed Apache-2.0. It adds 106 tokens to every session and 1,685 once invoked, about $0.0005 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
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…
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…