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-issuenpx skills add NVIDIA/OpenShell --skill create-github-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.00063 | $0.01103 |
| Opus 5 | $0.00032 | $0.00551 |
| Sonnet 5 | $0.00013 | $0.00221 |
| Haiku 4.5 | $0.00006 | $0.00110 |
Grade A, and why
create-github-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 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 — 153 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create GitHub Issue
Create issues on GitHub using the gh CLI. Issues must conform to the project's issue templates.
Prerequisites
The gh CLI must be authenticated (gh auth status).
Issue Templates
This project uses YAML form issue templates. When creating issues, match the template structure so the output aligns with what GitHub renders.
Bug Reports
Do not add a type label automatically. The body must include a User Story, Problem Statement, Impact / Why This Matters, and Acceptance Criteria, followed by bug-specific reproduction steps and environment details. Logs are optional and must be concise and redacted. Apply area or topic labels only when they are clearly known.
gh issue create \
--title "bug: <concise description>" \
--body "$(cat <<'EOF'
## User Story
As a <persona>, I want <capability or outcome>, so that <benefit or impact>.
## Problem Statement
<Summarize what is broken or missing in OpenShell's current behavior and when the issue occurs>
## Impact / Why This Matters
<Explain the consequences for users, the current workaround, and why that workaround is insufficient>
## Acceptance Criteria
- [ ] <observable outcome that demonstrates the bug is fixed>
## Reproduction Steps
1. <step>
2. <step>
## Environment
- OpenShell: <version>
- OS: <os>
- Runtime, deployment, or integration: <relevant details>
## Logs
<optional minimal, redacted output>
EOF
)"
Feature Requests
Do not add a type label automatically. The body must include a User Story, Problem Statement, Impact / Why This Matters, Proposed Design, Acceptance Criteria, and Alternatives Considered. The proposed design should define the user-facing workflow and externally observable behavior without prescribing internal implementation. Agent investigation is optional. Apply area or topic labels only when they are clearly known.
gh issue create \
--title "feat: <concise description>" \
--body "$(cat <<'EOF'
## User Story
As a <persona>, I want <capability or outcome>, so that <benefit or impact>.
## Problem Statement
<Summarize the capability or behavior missing from OpenShell today>
## Impact / Why This Matters
<Explain what users must do today, why it is insufficient, and the operational cost, risk, blocked workflow, or adoption barrier>
## Proposed Design
<The desired user-facing workflow and externally observable behavior, without prescribing internal implementation>
## Acceptance Criteria
- [ ] <specific, observable outcome>
## Alternatives Considered
<Other user-facing workflows or behaviors considered and why this approach best satisfies the user story>
## Agent Investigation
<Optional findings from codebase exploration>
EOF
)"
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 · 153 lines · 63 tokens per session scan A 2c6625b97418
create-github-issue is a skill published in the GitHub repository NVIDIA/OpenShell (8,421 stars, last pushed 2d ago), licensed Apache-2.0. It adds 63 tokens to every session and 1,103 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…