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/create-github-prnpx skills add NVIDIA/OpenShell --skill create-github-prgit 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.00056 | $0.01735 |
| Opus 5 | $0.00028 | $0.00868 |
| Sonnet 5 | $0.00011 | $0.00347 |
| Haiku 4.5 | $0.00006 | $0.00173 |
Grade A, and why
create-github-pr 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 yesterday.
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 — 252 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create GitHub Pull Request
Create pull requests on GitHub using the gh CLI.
Prerequisites
- The
ghCLI must be authenticated (gh auth status) - You must have commits on a branch that's pushed to the remote
- For issue-backed work, the branch should follow
<issue-number>-<description>/<username>. Exempt issue-less changes may use<description>/<username>.
Before Creating a PR
Check Config Documentation
If the branch changes gateway TOML parsing, [openshell.gateway] fields,
[openshell.drivers.<name>] fields, driver config defaults, or Helm rendering
of gateway.toml, verify that docs/reference/gateway-config.mdx is updated
in the same branch. If the change affects user-facing compute-driver setup,
also update docs/reference/sandbox-compute-drivers.mdx or the relevant
deployment docs.
Check Agent Infrastructure
Use the sync-agent-infra skill's maintenance map to identify related skill updates when the branch changes behavior, commands, or development workflows. Run its full consistency check when the branch adds, removes, or renames skills or crates; changes workflow relationships or skill coverage; modifies issue or PR templates; or changes agent cross-references. Resolve any drift before creating the PR.
Run Pre-commit Checks
Run the local pre-commit task before opening a PR:
mise run pre-commit
Verify Branch State
Before creating a PR, verify:
-
You're not on main - Never create PRs directly from main:
# Should NOT be "main" git branch --show-current -
Branch follows naming convention - Use
<issue-number>-<description>/<initials>for issue-backed work or<description>/<initials>for an exempt issue-less change.# Example: 1234-add-pagination/jd git branch --show-current -
Consider squashing commits - For cleaner history, squash related commits before pushing:
# Squash last N commits into one git reset --soft HEAD~N git commit -m "feat(component): description"
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.
- yesterday First seen · 252 lines · 56 tokens per session scan A 113e5015670a
create-github-pr is a skill published in the GitHub repository NVIDIA/OpenShell (8,421 stars, last pushed 2d ago), licensed Apache-2.0. It adds 56 tokens to every session and 1,735 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…