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/gator-gatenpx skills add NVIDIA/OpenShell --skill gator-gategit 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.16453 |
| Opus 5 | $0.00028 | $0.08226 |
| Sonnet 5 | $0.00011 | $0.03291 |
| Haiku 4.5 | $0.00006 | $0.01645 |
Grade B, and why
gator-gate scanned grade B with 2 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.
Strips warnings and disclaimersmediumAnti-refusal
Omitting safety caveats hides risk from the user and is a common jailbreak preamble.
`gator:in-review`; do not add Warnings. Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
Use REST-backed `gh api` for GitHub write actions inside gator sandboxes. Do not rely on `gh issue edit`, `gh pr edit`, or other high-level write commands when a REST path is available, because some of them use GraphQL m How it starts
The opening of the file, as written. The whole thing — 1,294 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Gator Gate
Validate OpenShell GitHub issues and pull requests for project fit, then monitor valid PRs until they are ready for maintainer approval.
This skill is a gating workflow. It can start from any issue or PR state, inspect the current gator:* label, and continue the correct next action.
Skill Location
Codex and other agent harnesses should load this skill from the repository path scripts/agents/gator/skills/gator-gate/SKILL.md. After this branch is merged, the canonical GitHub location is https://github.com/NVIDIA/OpenShell/blob/main/scripts/agents/gator/skills/gator-gate/SKILL.md.
Prerequisites
- The
ghCLI must be able to call GitHub APIs (gh api user --jq '.login') - You must be in the OpenShell repository root
- GitHub write permissions are required to apply labels, comment, close issues/PRs, or post
/ok to test
Do not use gh auth status as the authentication health check inside provider-backed sandboxes. Scoped provider tokens may be exposed as openshell:resolve:env:* placeholders and gh auth status probes endpoints outside the gator policy, causing false "token is invalid" reports even when allowed gh api and gh pr calls succeed. Use gh api user --jq '.login' and a repo-scoped probe instead.
Use REST-backed gh api for GitHub write actions inside gator sandboxes. Do not rely on gh issue edit, gh pr edit, or other high-level write commands when a REST path is available, because some of them use GraphQL mutations and gator policy allows GraphQL reads only. Do not fall back to curl for credentialed GitHub writes unless the active provider policy explicitly allows the curl binary for the same scoped endpoint. Preferred write shapes:
jq -Rs '{body:.}' comment.md > /tmp/comment.json
gh api --method POST repos/NVIDIA/OpenShell/issues/<number>/comments --input /tmp/comment.json --jq .html_url
gh api --method POST repos/NVIDIA/OpenShell/issues/<number>/labels -f labels[]="gator:<state>"
gh api --method DELETE repos/NVIDIA/OpenShell/issues/<number>/labels/gator%3Ablocked --silent || true
What ships with it
1 file 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.
- 2d ago First seen · 1,294 lines · 57 tokens per session scan B d80485fd553f
gator-gate 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 16,453 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 2 findings (strips warnings and disclaimers, makes network calls). 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…