agentmods.dev

OpenShell: Skill for Claude Code

.agents/skills/update-docs/SKILL.md

update-docs-from-commits is a skill for Claude Code, Codex from NVIDIA/OpenShell. It costs 80 tokens per session (2,381 once invoked), scanned A, original, Apache-2.0.

A documentation workflow that scans recent Git commits for user-facing changes and drafts or updates the matching documentation pages. Git commits are saved records of code changes.

In plain words
What is it for?
Use it before a release or after several changes to identify relevant commits, check the documentation contribution rules, and prepare updates in the docs tree.
Why use it?
It helps prevent the documentation from falling behind after features and fixes are added.

Skill for Claude CodeCodex ✓ vendor

Written for no agent in particular: nothing here depends on one. Also seen: installed under .agents/ (shared by several agents).

This is NVIDIA/OpenShell's own configuration. It tells Claude Code and Codex how to work on OpenShell itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything OpenShell configures →

not rated 21krepo +404 changed 1mo ago A scan SkillSpector: pass 80 tokens original Apache-2.0
View source ↗ NVIDIA/OpenShell docs.nvidia.com
About the project

OpenShell is a runtime for autonomous AI agents that executes them in sandboxed environments governed by declarative policies. It is used to restrict agents' access to files, credentials, data, and network resources, and the catalogue includes skills and workflows for operating and contributing to it.

NVIDIA/OpenShell · 21,172 stars · on GitHub · docs.nvidia.com

Reuse

Borrowing it

Nothing to install: this file belongs to NVIDIA/OpenShell. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/NVIDIA/OpenShell/main/.agents/skills/update-docs/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/NVIDIA/OpenShell

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for update-docs-from-commits

README.md
[![agentmods](https://agentmods.dev/badge/skills/nvidia/openshell/update-docs/github.svg)](https://agentmods.dev/skills/nvidia/openshell/update-docs)
Your own site
<a href="https://agentmods.dev/skills/nvidia/openshell/update-docs"><img src="https://agentmods.dev/badge/skills/nvidia/openshell/update-docs/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for update-docs-from-commits

Your own site · 80×15
<a href="https://agentmods.dev/skills/nvidia/openshell/update-docs"><img src="https://agentmods.dev/badge/skills/nvidia/openshell/update-docs.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 80 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,381 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What 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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00080 $0.02381
Opus 5.5 $0.00032 $0.00952
Sonnet 5.5 $0.00016 $0.00476
Haiku 4.5 $0.00008 $0.00238

Measured 1mo ago against content hash 51bcb8c29687, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 1mo 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.

.agents/skills/update-docs/SKILL.md · 189 lines

How it starts

The opening of the file, as written. The whole thing — 189 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.mdx before 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:

  1. Commit type: feat, fix, refactor, perf commits often change behavior. docs commits are already doc changes. chore, ci, test commits rarely need doc updates.
  2. Files changed: Changes to crates/openshell-cli/, python/, proto/, deploy/, gateway config parsing, driver config structs, or policy-related code are high-signal.
  3. 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/how-it-works/gateways/overview.mdx
crates/openshell-cli/ (sandbox commands) docs/how-it-works/sandboxes/overview.mdx
crates/openshell-cli/ (provider commands) docs/how-it-works/providers/overview.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/how-it-works/gateways/configuration.mdx
crates/openshell-server/src/cli.rs gateway config merge/default behavior docs/how-it-works/gateways/configuration.mdx
crates/openshell-driver-*/ config structs or driver defaults docs/how-it-works/gateways/configuration.mdx, docs/how-it-works/sandboxes/runtimes.mdx
deploy/helm/openshell/templates/gateway-config.yaml docs/how-it-works/gateways/configuration.mdx, docs/how-it-works/sandboxes/runtimes.mdx, Helm docs if values change
Proxy or policy code docs/how-it-works/policies/overview.mdx, docs/how-it-works/policies/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/how-it-works/gateways/overview.mdx, docs/about/architecture.mdx
Sandbox image behavior docs/how-it-works/sandboxes/overview.mdx

Read the full file on GitHub · 189 lines

Changes

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.

  1. 1mo ago Changed 51bcb8c29687
  2. 1mo ago Changed · +2 lines c792f4ab5f8d
  3. 1mo ago Changed 052451a53f88
  4. 1mo ago Changed ca70a18635ee
  5. 2mo ago Changed · +2 lines 80fd652ee492
  6. 2mo ago First seen · 185 lines · 80 tokens per session scan A 0a0868233d6d

Subscribe to this mod's changes

update-docs-from-commits is a skill published in the GitHub repository NVIDIA/OpenShell (21,172 stars, last pushed yesterday), licensed Apache-2.0. It adds 80 tokens to every session and 2,381 once invoked, about $0.0003 per session on Opus 5.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.

Git and workflowWriting and docs
Related

update-docs-from-commits compared with skills from other repositories

update-docs-from-commits next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
update-docs-from-commitsNVIDIA/OpenShellSkill21kyesterdayApache-2.0A80Claude Code, Codex
merge-batchdiegosouzapw/OmniRouteSkill83k5d agoMITA46Claude Code
prowler-commitprowler-cloud/prowlerSkill15kyesterdayApache-2.0A44Claude Code, Codex
gh-auth-isolationgithub/gh-awSkill5.6ktodayMITA20Claude Code, Codex
github-skillzeenie-ai/OpenCompanySkill1.1kyesterdayMITA51Claude Code
comet-githubrpamis/cometSkill3.3ktodayMITA72Claude Code, Codex
release-helperSahir619/fable-methodSkill2.3k1mo agoMITA43Claude Code