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/fix-security-issuenpx skills add NVIDIA/OpenShell --skill fix-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.00070 | $0.02885 |
| Opus 5 | $0.00035 | $0.01443 |
| Sonnet 5 | $0.00014 | $0.00577 |
| Haiku 4.5 | $0.00007 | $0.00288 |
Grade A, and why
fix-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 — 321 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fix Security Issue
Implement a code fix for a security issue that has already been reviewed by the review-security-issue skill.
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 scan mode it must also haveagent:implementation-requested; for a direct user request, warn if that workflow label is missing and continue without changing it. - The issue must have a prior security review comment (posted by
review-security-issue) with a Legitimate concern determination and a remediation plan
Agent Comment Marker
All PR descriptions and comments posted by this skill must begin with the following marker line:
> **🔧 security-fix-agent**
This distinguishes fix-agent content from review-agent comments (🔒 security-review-agent) and human comments.
Step 1: Identify the Issue
The user may provide an issue number directly, or ask the agent to find issues to fix.
If an issue number is provided
Strip any leading # and proceed to Step 2 with that issue ID. The user's explicit fix request authorizes implementation. If agent:implementation-requested is absent, warn that the expected workflow label is missing and continue without changing it.
If no issue number is provided
Scan for open issues labeled topic:security and agent:implementation-requested:
gh issue list --label "topic:security" --label "agent:implementation-requested" --state open --json number,title,labels,updatedAt
- If no issues are found, report to the user that there are no security issues ready for fixing and stop.
- If one issue is found, proceed to Step 2 with that issue.
- If multiple issues are found, list them for the user and ask which one to work on. If the user said to handle all of them, process them sequentially (one full fix cycle per issue).
Step 2: Fetch the Issue and Validate Labels
Fetch the issue details:
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 · 321 lines · 70 tokens per session scan A 1d95042bfb50
fix-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 70 tokens to every session and 2,885 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…