ASPIRE: Instructions file for Codex

AGENTS.md

ASPIRE AGENTS.md is an instructions file for Codex, OpenCode from NVlabs/ASPIRE. It costs 1,500 tokens per session, scanned A, original, Apache-2.0.

An operating guide for ASPIRE, a system for running robot-learning simulation experiments, including LIBERO-Pro and BEHAVIOR-1K tasks. It defines which project instructions to read and what must be checked before starting.

In plain words
What is it for?
Use it before setting up or running the specified simulations, evaluations, replays, or experiment batches, and when preparing the required preflight report.
Why use it?
It prevents experiments from running with missing services, credentials, model files, hardware settings, or unclear output locations.

Instructions file for CodexOpenCode

Written for Codex and OpenCode: the file is AGENTS.md.

This is NVlabs/ASPIRE's own configuration. It tells Codex and OpenCode how to work on ASPIRE 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 ASPIRE configures →

Reuse

Borrowing it

Nothing to install: this file belongs to NVlabs/ASPIRE. 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/NVlabs/ASPIRE/main/AGENTS.md
Clone the repo
git clone --depth 1 https://github.com/NVlabs/ASPIRE

Made for: Codex, OpenCode.

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

README.md
[![agentmods](https://agentmods.dev/badge/instructions/nvlabs/aspire/agents-md/github.svg)](https://agentmods.dev/instructions/nvlabs/aspire/agents-md)
Your own site
<a href="https://agentmods.dev/instructions/nvlabs/aspire/agents-md"><img src="https://agentmods.dev/badge/instructions/nvlabs/aspire/agents-md/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 ASPIRE AGENTS.md

Your own site · 80×15
<a href="https://agentmods.dev/instructions/nvlabs/aspire/agents-md"><img src="https://agentmods.dev/badge/instructions/nvlabs/aspire/agents-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 1,500 This file is loaded in full into every session.
When invoked 1,500 The same file — it is already loaded in full.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
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.01500 $0.01500
Opus 5.5 $0.00600 $0.00600
Sonnet 5.5 $0.00300 $0.00300
Haiku 4.5 $0.00150 $0.00150

Measured 21d ago against content hash 69553407139f, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

ASPIRE 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 21d 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.md · 132 lines

How it starts

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

Real YAM System 2

These execution rules apply when operating the robot through an already configured ASPIRE CAP MCP session. For installation and service startup, use the operator runbook.

System 2 owns the operator goal, task-level reasoning, tool selection, supervision, and recovery. Act through registered native mcp__cap__* tools; never bypass them with source edits, ad-hoc robot code, or shell-wrapped motion.

Instruction priority and skills

The user's instructions take precedence over guidelines provided in a skill. If explicit user instructions conflict with a skill's instructions, prioritize the user's instructions. Use this file for shared execution rules; skills add task- and tool-specific procedures.

Infer routine details. Ask for input when a missing choice materially changes the physical outcome or no safe registered recovery remains.

At fresh-session startup, read cap-tool-usage once before the first robot command. For a cube task, read manipulation-tasks and its linked task context and cube guide before acting. Do not reread an unchanged skill later.

For bottle/pill or cup-stacking tasks, read the matching recipe linked from manipulation-tasks before acting; do not load unrelated recipes.

Native MCP schemas are authoritative for tool names and arguments. Discover the capability graph once per runtime and reuse it. Do not inspect implementation source or invent a tool when a contract is already exposed.

When using low-level cap action tools like move_to_pose, reduce the pauses between action tool calling. The system need more continous execution without significant delay.

Initiative and follow-through

When the user expresses intent to perform new work or fix an existing issue, persist until the user's intended goal is complete. Progress autonomously towards the user's goal unless they are clearly destructive or irreversible.

Read the full file on GitHub · 132 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. 21d ago Changed · +51 lines · +499 tokens per session 69553407139f
  2. 2mo ago First seen · 81 lines · 1,001 tokens per session scan A 7b2159f29a46

Subscribe to this mod's changes

ASPIRE AGENTS.md is an instructions file published in the GitHub repository NVlabs/ASPIRE (959 stars, last pushed 22d ago), licensed Apache-2.0. It adds 1,500 tokens to every session, about $0.0060 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.

Related

ASPIRE AGENTS.md compared with instructions from other repositories

ASPIRE AGENTS.md next to 6 instructions from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
ASPIRE AGENTS.mdNVlabs/ASPIREInstructions file95922d agoApache-2.0A1,500Codex, OpenCode
vscode buildNext.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA9,719GitHub Copilot
next.js AGENTS.mdvercel/next.jsInstructions file143kyesterdayMITA7,461Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchainInstructions file149kyesterdayMITA4,680Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA5,516GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscodeInstructions file195kyesterdayMITA3,093GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harnessInstructions file274k2d agoMITA4,313Codex, OpenCode