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/nvidia/openshell/review-security-issuenpx skills add NVIDIA/OpenShell --skill review-security-issuegit clone --depth 1 https://github.com/NVIDIA/OpenShellWhat 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.00057 | $0.01839 |
| Opus 5 | $0.00028 | $0.00920 |
| Sonnet 5 | $0.00011 | $0.00368 |
| Haiku 4.5 | $0.00006 | $0.00184 |
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 2d 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 — 195 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Review Security Issue
Review an issue that outlines a security, vulnerability, or privacy concern.
Prerequisites
- The
ghCLI must be authenticated (gh auth status) - You must be in a git repository with a GitHub remote
- The issue must have
topic:security. In unattended queue mode it must also haveagent:plan-requested; for a direct user request, warn if that workflow label is missing and continue without changing it.
Agent Comment Marker
All comments posted by this skill must begin with the following marker line so that prior reviews can be detected and human comments can be distinguished from agent comments:
> **🔒 security-review-agent**
This marker is used in Step 2 to detect prior reviews and in Step 5 to distinguish agent comments from human comments.
Step 1: Fetch the Issue
The user will provide an issue ID (e.g., #42 or 42). Strip any leading # and fetch the issue contents.
gh issue view <id>
To also retrieve the full issue body as JSON (useful for parsing):
gh issue view <id> --json title,body,state,labels,author
Step 2: Check if Review is Needed
First, check the issue's labels from the metadata fetched in Step 1.
- If the issue has
agent:implementation-requested, the issue has already been reviewed and a human authorized remediation. There is no review to perform. Suggest usingfix-security-issueand stop. - If
topic:securityis missing, report that this specialized skill only reviews security issues and stop. - If this is queue mode and
agent:plan-requestedis missing, report that the issue is not ready for unattended pickup and stop. - If the user directly requested review of this issue, warn that
agent:plan-requestedis missing, then proceed without it. Never add or offer to add the human-only request label.
Next, fetch existing comments on the issue:
gh issue view <id> --json comments --jq '.comments[].body'
Search the comments for the agent marker (> **🔒 security-review-agent**).
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.
- 2d ago First seen · 195 lines · 57 tokens per session scan A 667361dde364
review-security-issue is a skill published in the GitHub repository NVIDIA/OpenShell (8,421 stars, last pushed 3d ago), licensed Apache-2.0. It adds 57 tokens to every session and 1,839 once invoked, about $0.0003 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.
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…
babysit-pr
Babysit a GitHub pull request after creation by continuously polling review comments, CI checks/workflow runs, and mergeability state until the PR is merged/closed or user help is required. Diagnose failures, retry likely flaky failures up to 3 times, auto-fix/push branch-related issues when appropriate, and keep…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
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-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…