agentmods.dev

OpenShell AGENTS.md

A project instruction file that tells coding agents how OpenShell is organized, which skills and workflows to use, and what the project does. OpenShell provides safe, isolated environments for autonomous AI agents.

In plain words
What is it for?
Use it when agents need to triage issues, plan work, follow connected workflows, or understand OpenShell's architecture and contribution rules.
Why use it?
It gives agents shared context on every interaction, reducing misunderstandings about the project, its structure, and its development process.

Instructions file for CodexOpenCode

8.4k 2d ago A scan 4,544 tokens original Apache-2.0
View the source file NVIDIA/OpenShell
Install

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.

agentmods
npx agentmods add instructions/nvidia/openshell/agents-md
Clone the repo
git clone --depth 1 https://github.com/NVIDIA/OpenShell

Made for: Codex, OpenCode.

Per session 4,544 This file is loaded in full into every session.
When invoked 4,544 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
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 $0.04544 $0.04544
Opus 5 $0.02272 $0.02272
Sonnet 5 $0.00909 $0.00909
Haiku 4.5 $0.00454 $0.00454

Measured yesterday against content hash 9cf9f02a4861, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

OpenShell AGENTS.md 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.

AGENTS.md · 270 lines

How it starts

The opening of the file, as written. The whole thing — 270 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Agent Instructions

This file is the primary instruction surface for agents contributing to OpenShell. It is injected into your context on every interaction — keep that in mind when proposing changes to it.

See CONTRIBUTING.md for build instructions, task reference, project structure, and the full agent skills table.

Project Identity

OpenShell is built agent-first. We design systems and use agents to implement them — this is not vibe coding. The product provides safe, sandboxed runtimes for autonomous AI agents, and the project itself is built using the same agent-driven workflows it enables.

Skills

Agent skills live in .agents/skills/. Your harness can discover and load them natively — do not rely on this file for a full inventory. The detailed skills table is in CONTRIBUTING.md (for humans).

Workflow Chains

These pipelines connect skills into end-to-end workflows. Individual skill files don't describe these relationships.

  • Community inflow: triage-issue → human disposition and roadmap placement → create-spike when needed → build-from-issue
    • Triage establishes facts and marks technically valid issues state:validated. A human signals that the project should pursue the work by applying state:accepted or placing the issue on the roadmap. The agent:* labels support unattended agents that scan for queued work: a human queues a plan with agent:plan-requested, the agent returns agent:plan-ready, and a human queues implementation with agent:implementation-requested. A direct user request to an agent authorizes the requested phase even when the expected lifecycle or workflow labels are missing or incomplete; the agent warns about the discrepancies and continues without changing the labels.
  • Internal development: create-spike → human disposition and roadmap placement → build-from-issue
    • Spike explores feasibility and marks its issue state:validated when sufficient evidence exists. A human accepts it with state:accepted or roadmap placement, or declines it, and optionally queues it through the agent:* workflow or directs an agent to it. A direct request proceeds after warning about missing or incomplete expected labels.
  • Security: review-security-issue → fix-security-issue
    • General build agents must not process topic:security issues. For unattended processing, a human queues specialized review with agent:plan-requested; review produces a severity assessment and remediation plan; a human queues remediation with agent:implementation-requested. On direct requests to the specialized skills, missing workflow labels produce a warning rather than blocking the requested phase.
  • Policy iteration: openshell-cli → generate-sandbox-policy
    • CLI manages the sandbox lifecycle; policy generation authors the YAML constraints.

Read the full file on GitHub · 270 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. yesterday First seen · 270 lines · 4,544 tokens per session scan A 9cf9f02a4861

Subscribe to this mod's changes

OpenShell AGENTS.md is an instructions file published in the GitHub repository NVIDIA/OpenShell (8,421 stars, last pushed 2d ago), licensed Apache-2.0. It adds 4,544 tokens to every session, about $0.0227 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.

PlanningProductivity
Related

Other instructions, from other repositories

codex AGENTS.md

AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.

openai/codex · 5,182 tokens

buildNext

Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).

microsoft/vscode · 6,785 tokens

next.js AGENTS.md

Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.

vercel/next.js · 7,296 tokens

vscode oss-third-party-notices.instructions.md

Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).

microsoft/vscode · 5,001 tokens

spec-kit AGENTS.md

Instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.

github/spec-kit · 7,040 tokens

langchain AGENTS.md

Instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.

langchain-ai/langchain · 4,345 tokens