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/debug-inferencenpx skills add NVIDIA/OpenShell --skill debug-inferencegit 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.00114 | $0.04159 |
| Opus 5 | $0.00057 | $0.02080 |
| Sonnet 5 | $0.00023 | $0.00832 |
| Haiku 4.5 | $0.00011 | $0.00416 |
Grade A, and why
debug-inference scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
openshell sandbox create -- curl https://inference.local/v1/chat/completions --json '{"messages":[{"role":"user","content":"hello"}],"max_tokens":10}' How it starts
The opening of the file, as written. The whole thing — 409 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Debug Inference
Diagnose why OpenShell inference is failing and recommend exact fix commands.
Use openshell CLI commands to inspect the active gateway, provider records, managed inference config, and sandbox behavior. Use a short sandbox probe when needed to confirm end-to-end routing.
Overview
OpenShell supports three inference paths. Diagnose the correct one first.
- Managed inference through
https://inference.local- Configured by
openshell inference set - Shared by every sandbox on the active gateway
- Credentials and model are injected by OpenShell
- Configured by
- Direct external inference to hosts like
api.openai.com- Controlled by
network_policies - Requires the application to call the external host directly
- Requires provider attachment and network access to be configured separately
- Controlled by
- System inference used by platform functions
- Configured by
openshell inference set --system - Uses the
sandbox-systemroute - Consumed in-process by the sandbox supervisor and not exposed to sandbox user code through
inference.local
- Configured by
For local or self-hosted engines such as Ollama, vLLM, SGLang, TRT-LLM, and many NIM deployments, the most common managed inference pattern is an openai provider with OPENAI_BASE_URL pointing at a host the gateway can reach.
Prerequisites
openshellis on the PATH- The active gateway is running
- You know the failing setup, or can infer it from commands and config
Tools Available
Use these commands first:
# Which gateway is active, and can the CLI reach it?
openshell status
# Show both the user-facing and system inference routes
openshell inference get
# Show only the supervisor-only system route
openshell inference get --system
# Inspect the provider record referenced by the relevant route
openshell provider get <provider-name>
# Inspect gateway topology details when remote/local confusion is suspected
openshell gateway info
# Run a minimal end-to-end probe from a sandbox
openshell sandbox create -- curl https://inference.local/v1/chat/completions --json '{"messages":[{"role":"user","content":"hello"}],"max_tokens":10}'
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 · 409 lines · 114 tokens per session scan A 9b671793b0f0
debug-inference is a skill published in the GitHub repository NVIDIA/OpenShell (8,421 stars, last pushed 2d ago), licensed Apache-2.0. It adds 114 tokens to every session and 4,159 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 1 finding (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…