What is review-security-issue?

A reviewer for GitHub issues that report security, vulnerability, or privacy concerns. It examines the issue and decides whether the claim should be addressed or marked as not planned for fixing.

Use it to fetch and assess a labeled GitHub security issue, check whether it needs a response, and provide a marked review comment when appropriate.

Security reports can be incomplete, mistaken, or serious; a structured review helps separate real risks from issues that do not require a code change.

How NVIDIA/OpenShell configures Claude Code and Codex

About the project

OpenShell is a runtime for autonomous AI agents that executes them in sandboxed environments governed by declarative policies. It is used to restrict agents' access to files, credentials, data, and network resources, and the catalogue includes skills and workflows for operating and contributing to it.

NVIDIA/OpenShell · 21,172 stars · on GitHub · docs.nvidia.com

Reuse

Borrowing it

Nothing to install: this file belongs to NVIDIA/OpenShell. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/NVIDIA/OpenShell/main/.agents/skills/review-security-issue/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/NVIDIA/OpenShell

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/nvidia/openshell/review-security-issue/github.svg)](https://agentmods.dev/skills/nvidia/openshell/review-security-issue)

Your own site

<a href="https://agentmods.dev/skills/nvidia/openshell/review-security-issue"><img src="https://agentmods.dev/badge/skills/nvidia/openshell/review-security-issue/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/nvidia/openshell/review-security-issue"><img src="https://agentmods.dev/badge/skills/nvidia/openshell/review-security-issue.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 468 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. Third-party audits

Snyk warn 7 Sept 2026
NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

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.00025	$0.00468
Opus 5.5	$0.00010	$0.00187
Sonnet 5.5	$0.00005	$0.00094
Haiku 4.5	$0.00003	$0.00047

Measured 9d ago against content hash 6c50d6d33dbc, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

review-security-issue 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 9d 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.

.agents/skills/review-security-issue/SKILL.md · 21 lines

How it starts

The opening of the file, as written. The whole thing — 21 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Review Security Issue

Review a security concern through its authorized private workflow. Do not file or expand a vulnerability in a public issue; follow SECURITY.md. A direct request to review authorizes review only, not remediation. For unattended review, verify authorization from maintainer direction and accessible discussion; for issues, also inspect current state:* label descriptions and assignments.

Assess

Fetch the requested source. For a GHSA, use gh api --method GET repos/OWNER/REPO/security-advisories/GHSA-ID and read any supplied private discussion or fix links. The advisory payload does not include its discussion; report inaccessible prior discussion as unverified. For an issue, use gh issue view <id> --json title,body,state,labels,comments and follow Label Discovery in CONTRIBUTING.md; GHSA lifecycle states are not issue labels. Verify authorization and check whether a prior review already answers the request.
Check the required advisory report format and supporting reproduction or concrete code evidence. If either is missing, return a concise request for the missing sections or evidence before technical triage. Do not fill gaps with assumptions or treat scanner output as proof.
Inspect affected code and verify the claim. Assess impact, exploitability, prerequisites, affected surface, and a concrete attack scenario. Separate reported claims, code inspection, and reproduced results; check the attacker's existing authority and give a severity with rationale.
If actionable, propose a remediation plan with code areas, safe rollout, and focused tests. If not actionable, explain the evidence and recommended disposition. Do not decide product acceptance or silently close the issue.
Post the review or revision request only when the request authorizes posting. Begin the comment with > **🔒 security-review-agent** so later reviews can detect it. Keep sensitive details in the authorized private venue.

Read the full file on GitHub · 21 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.

9d ago Changed · +1 lines · +5 tokens per session 6c50d6d33dbc
1mo ago Changed 2ca87e46aa9f
1mo ago Changed · -177 lines · -37 tokens per session bebed2e36e56
2mo ago Changed · +2 lines 58e2f87f6adf
2mo ago First seen · 195 lines · 57 tokens per session scan A 667361dde364

Subscribe to this mod's changes

review-security-issue is a skill published in the GitHub repository NVIDIA/OpenShell (21,172 stars, last pushed yesterday), licensed Apache-2.0. It adds 25 tokens to every session and 468 once invoked, about $0.0001 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-30.