cuopt AGENTS.md

A guide for AI agents working with NVIDIA cuOpt, an optimization engine for solving planning problems. It explains the skills directory and separates user guidance from instructions for changing cuOpt itself.

In plain words
What is it for?
Use it for cuOpt routing, linear or quadratic optimization, installation, server work, solver development, CUDA or C++ changes, Python work, and contribution tasks.
Why use it?
It helps the agent choose the right instructions for using cuOpt or developing it. It also requires unclear requests to be clarified or solved for every reasonable interpretation.

Instructions file for CodexOpenCode

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/cuopt/agents-md
Clone the repo
git clone --depth 1 https://github.com/NVIDIA/cuopt

Made for: Codex, OpenCode.

Per session 913 This file is loaded in full into every session.
When invoked 913 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.00913 $0.00913
Opus 5 $0.00456 $0.00456
Sonnet 5 $0.00183 $0.00183
Haiku 4.5 $0.00091 $0.00091

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

Security

Grade A, and why

cuopt 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 · 54 lines

How it starts

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

AGENTS.md — cuOpt AI Agent Entry Point

AI agent skills for NVIDIA cuOpt optimization engine. Skills live in skills/ (repo root) and use a flat layout: per domain, a concept skill (formulation / problem types) plus implementation skills — typically one per interface (Python, C, CLI, server), or consolidated when the content is shared across interfaces (e.g. installation). Skills evolve through agent interactions — see skills/cuopt-skill-evolution/ for the evolution workflow.

🔒 MANDATORY — Ambiguity: When the problem could be read more than one way, you MUST either ask the user to clarify or solve every plausible interpretation and report all outcomes. Never pick one interpretation silently.

Skills directory (flat)

Rules

  • skills/cuopt-user-rules/ — Base rules for end users calling cuOpt (routing, LP, MILP, QP, install, server). Not for cuOpt internals — see skills/cuopt-developer/. Read first for user-facing tasks; choose skills from the index below by task and interface.
  • skills/cuopt-developer/ — Modify, build, test, debug, and contribute to cuOpt internals (C++/CUDA, Python, server, CI). Use for solver internals, PRs, DCO, and code conventions. For VRP dimension work (combine invariants, fwd/bwd propagation, new constraints/objectives in the routing engine), read skills/cuopt-developer/references/vrp_skills.md in addition to SKILL.md.
  • skills/cuopt-skill-evolution/ — Skill evolution: after solving a non-trivial problem, propose skill updates to capture generalizable learnings.

Common (concepts only; no API code)

  • skills/cuopt-numerical-optimization-formulation/ — LP / MILP / QP: concepts + problem parsing + common formulation patterns
  • skills/cuopt-multi-objective-exploration/ — Multi-objective: trace + interpret the Pareto frontier across competing objectives (ε-constraint / weighted-sum over repeated cuOpt solves)

Installation

  • skills/cuopt-install/ — User install for Python, C, and server (pip, conda, Docker, verification). For building cuOpt from source, see skills/cuopt-developer/.

Read the full file on GitHub · 54 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 · 54 lines · 913 tokens per session scan A beb5c6e963c3

Subscribe to this mod's changes

cuopt AGENTS.md is an instructions file published in the GitHub repository NVIDIA/cuopt (1,032 stars, last pushed 3d ago), licensed Apache-2.0. It adds 913 tokens to every session, about $0.0046 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.

Related

Other instructions, from other repositories