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/update-docsnpx skills add NVIDIA/OpenShell --skill update-docsgit 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.00080 | $0.02155 |
| Opus 5 | $0.00040 | $0.01077 |
| Sonnet 5 | $0.00016 | $0.00431 |
| Haiku 4.5 | $0.00008 | $0.00215 |
Grade A, and why
update-docs-from-commits 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 — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update Docs from Commits
Scan recent git history for commits that affect user-facing behavior and draft documentation updates for each.
Prerequisites
- You must be in the OpenShell git repository.
- The published docs tree must exist under
docs/. - Read
docs/CONTRIBUTING.mdxbefore writing any content. It contains the current style guide and formatting rules.
When to Use
- After a batch of features or fixes has landed and docs may be stale.
- Before a release, to catch any doc gaps.
- When a contributor asks "what docs need updating?"
Step 1: Identify Relevant Commits
Determine the commit range. The user may provide one explicitly (e.g., "since v0.2.0" or "last 30 commits"). If not, default to commits since the head of the main branch.
# Commits since a tag
git log v0.2.0..HEAD --oneline --no-merges
# Or last 50 commits
git log -50 --oneline --no-merges
Filter to commits that are likely to affect docs. Look for these signals:
- Commit type:
feat,fix,refactor,perfcommits often change behavior.docscommits are already doc changes.chore,ci,testcommits rarely need doc updates. - Files changed: Changes to
crates/openshell-cli/,python/,proto/,deploy/, gateway config parsing, driver config structs, or policy-related code are high-signal. - Ignore: Changes limited to
tests/,e2e/,.github/,tasks/, or internal-only modules.
# Show files changed per commit to assess impact
git log v0.2.0..HEAD --oneline --no-merges --name-only
Step 2: Map Commits to Doc Pages
For each relevant commit, determine which doc page(s) it affects. Use this mapping as a starting point:
| Code area | Likely doc page(s) |
|---|---|
crates/openshell-cli/ (gateway commands) |
docs/sandboxes/manage-gateways.mdx |
crates/openshell-cli/ (sandbox commands) |
docs/sandboxes/manage-sandboxes.mdx |
crates/openshell-cli/ (provider commands) |
docs/sandboxes/manage-providers.mdx |
crates/openshell-cli/ (new top-level command) |
May need a new page or docs/reference/ entry |
crates/openshell-server/src/config_file.rs or gateway TOML parsing |
docs/reference/gateway-config.mdx |
crates/openshell-server/src/cli.rs gateway config merge/default behavior |
docs/reference/gateway-config.mdx |
crates/openshell-driver-*/ config structs or driver defaults |
docs/reference/gateway-config.mdx, docs/reference/sandbox-compute-drivers.mdx |
deploy/helm/openshell/templates/gateway-config.yaml |
docs/reference/gateway-config.mdx, docs/reference/sandbox-compute-drivers.mdx, Helm docs if values change |
| Proxy or policy code | docs/sandboxes/policies.mdx, docs/reference/policy-schema.mdx |
| Inference code | docs/inference/configure.mdx |
python/ (SDK changes) |
docs/reference/ or docs/get-started/quickstart.mdx |
proto/ (API changes) |
docs/reference/ |
deploy/ (Dockerfile, Helm) |
docs/sandboxes/manage-gateways.mdx, docs/about/architecture.mdx |
| Community sandbox definitions | docs/sandboxes/community-sandboxes.mdx |
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 · 185 lines · 80 tokens per session scan A 0a0868233d6d
update-docs-from-commits is a skill published in the GitHub repository NVIDIA/OpenShell (8,421 stars, last pushed 3d ago), licensed Apache-2.0. It adds 80 tokens to every session and 2,155 once invoked, about $0.0004 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…