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 skills add openshift-eng/ai-helpers --skill review-plugin-cspgit clone --depth 1 https://github.com/openshift-eng/ai-helpersWrote 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/openshift-eng/ai-helpers/review-plugin-csp)<a href="https://agentmods.dev/skills/openshift-eng/ai-helpers/review-plugin-csp"><img src="https://agentmods.dev/badge/skills/openshift-eng/ai-helpers/review-plugin-csp/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.
<a href="https://agentmods.dev/skills/openshift-eng/ai-helpers/review-plugin-csp"><img src="https://agentmods.dev/badge/skills/openshift-eng/ai-helpers/review-plugin-csp.svg" alt="Reviewed on agentmods" width="80" 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.00045 | $0.05788 |
| Opus 5.5 | $0.00018 | $0.02315 |
| Sonnet 5.5 | $0.00009 | $0.01158 |
| Haiku 4.5 | $0.00005 | $0.00579 |
Grade A, and why
review-plugin-csp 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 7d 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 — 181 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review Console plugin CSP compatibility
Statically inspect a Console dynamic plugin for code, configuration and resource patterns that conflict with a given Content Security Policy, and produce a findings report with file locations, affected directives and migration steps.
This skill reviews repositories and build artifacts. It does not start Console, deploy a plugin, drive a browser, execute application workflows or collect/import browser violation reports. Users do not need to generate such reports. Its findings are predictions based on static evidence, not runtime confirmation.
Background
Content Security Policy (CSP) is a browser security mechanism delivered via an HTTP response header. The browser applies the policy to the document served with that header, controlling which sources of scripts, styles, images, connections and other resources are permitted. OpenShift Console's Go backend (pkg/server/server.go) sets the CSP header on the HTML document response — the policy is not stored in the HTML itself. Dynamic plugins load over the network at runtime via Module Federation and execute within the Console document — so the Console's CSP governs all plugin code. Plugin assets are proxied through the Console backend at /api/plugins/<name>/, making them same-origin ('self'). A plugin's spec.contentSecurityPolicy in its ConsolePlugin CR declares additional source allowances that the console-operator aggregates into the document-wide policy; this is not per-plugin isolation.
Usage
/console:review-plugin-csp [plugin-path] [--policy-file path] [--console-ref git-ref]
plugin-pathdefaults to the current repository.--policy-file(optional) supplies CSP directive values or captured response-header lines from a running Console. Prefer the authenticated Console HTML document response in browser DevTools Network; a saved HTML file does not preserve HTTP headers, and an unauthenticated request may return an OAuth redirect. A supplied effective policy takes precedence over the source-derived baseline; retain all CSP headers and their enforcing/report-only names.--console-ref(optional) specifies an OpenShift Console Git revision. Without it, resolve the currentmainHEAD ofopenshift/consoleduring the review and record its commit SHA; do not silently use a potentially stale localmain.
What ships with it
2 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.
- 7d ago First seen · 181 lines · 45 tokens per session scan A 6d745a5d9b1a
review-plugin-csp is a skill published in the GitHub repository openshift-eng/ai-helpers (121 stars, last pushed today), licensed Apache-2.0. It adds 45 tokens to every session and 5,788 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-10-15.
Other skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…
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…