DART is an open-source C++23 physics engine that simulates the movement and interactions of articulated rigid-body systems for robotics, animation, and machine learning. Researchers and developers use it for kinematics, dynamics, collision handling, constraints, and loading robot models, with C++ and Python interfaces. The catalogue add-ons support workflows built around this engine.
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/dartsim/dart/dart-docs-updatenpx skills add dartsim/dart --skill dart-docs-updategit clone --depth 1 https://github.com/dartsim/dartWrote 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.
[](https://agentmods.dev/skills/dartsim/dart/dart-docs-update)<a href="https://agentmods.dev/skills/dartsim/dart/dart-docs-update"><img src="https://agentmods.dev/badge/skills/dartsim/dart/dart-docs-update.svg" alt="Measured on agentmods" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00019 | $0.00685 |
| Opus 5 | $0.00010 | $0.00342 |
| Sonnet 5 | $0.00004 | $0.00137 |
| Haiku 4.5 | $0.00002 | $0.00068 |
Grade A, and why
dart-docs-update 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 today.
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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
dart-docs-update
Use this skill in Codex to run the DART dart-docs-update workflow. The editable
workflow source lives in .claude/commands/; this file is its generated adapter
in the shared .agents/skills/ catalog.
Invocation
- Claude Code/OpenCode:
/dart-docs-update <arguments> - Codex:
$dart-docs-update <arguments>
Treat the text after the skill name as $ARGUMENTS. When the workflow
references $1, $2, etc., map those to the positional values supplied by the
user.
Command Body
Update documentation: $ARGUMENTS
Required Reading
@AGENTS.md @docs/README.md @docs/AGENTS.md @docs/information-architecture.md @docs/ai/principles.md @docs/ai/verification.md
For AI instruction or workflow changes, follow the owner read order in
docs/ai/README.md; read the relevant tool section of
docs/onboarding/ai-tools.md only when compatibility is affected. Load
docs/onboarding/changelog.md when making the closeout changelog decision.
Workflow
- Create a branch from the target branch:
git checkout -b docs/<topic> origin/main - Edit docs and AI workflow sources only:
- Regular docs:
docs/**,README.md,AGENTS.md,CONTRIBUTING.md, andCHANGELOG.mdwhendart-changelogrequires a release-note entry - AI source files:
.claude/commands/**,.claude/skills/**
- Regular docs:
- For AI workflow changes, edit
.claude/sources and runpixi run sync-ai-commands; do not hand-edit generated.agents/skills/or.opencode/command/files (.codex/is a maintained source) - Classify new or moved docs by lifecycle first, then audience, then topic,
using
docs/information-architecture.md. For AI docs, keep always-loaded entrypoints compact: improve owner placement or pointers instead of duplicating procedures. - Update indexes and cross-references that point to changed docs
- Use
docs/ai/verification.mdto select the docs-only or AI docs/adapters gate set, then runpixi run lintbefore committing - Invoke the
dart-changelogroutine for theCHANGELOG.mddecision and any required entry. - Ask for explicit maintainer/user approval before pushing or opening the PR.
After approval, use
.github/PULL_REQUEST_TEMPLATE.mdand the proper milestone.
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.
- today Changed · +3 lines 1b435c07a1b1
- 2d ago Changed ea6d98004902
- 4d ago First seen · 68 lines · 19 tokens per session scan A 9f2117ba1a36
dart-docs-update is a skill published in the GitHub repository dartsim/dart (1,201 stars, last pushed today), licensed BSD-2-Clause. It adds 19 tokens to every session and 685 once invoked, about $0.0001 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-09-01.
Other skills, from other repositories
evaluating-cosmos-policy
Evaluates NVIDIA Cosmos Policy on LIBERO and RoboCasa simulation environments. Use when setting up cosmos-policy for robot manipulation evaluation, running headless GPU evaluations with EGL rendering, or profiling inference latency on cluster or local GPU machines.
smui
Local copy of the smui ("spacemolt") design system ( ), adapted for the CAD Viewer. smui is a Nord-inspired terminal aesthetic for shadcn/ui with light and dark modes: sharp edges, monospace everything. Read this whole document before restyling viewer UI.
cad-viewer
Start CAD Viewer and return review links for CAD and robot-description files. Use when visually reviewing .step, .stp, .glb, .stl, .3mf, .dxf, .urdf, .srdf, or .sdf files, especially when handed off from CAD, URDF, SRDF, or SDF generation skills.
urdf
URDF robot description authoring and validation. Use when creating, editing, inspecting, validating, or debugging .urdf files, robot links, joints, limits, inertials, visual/collision geometry, mesh references, frame conventions, or robot-description artifacts. Use the SRDF skill for MoveIt2 semantic groups and…
step-parts
Find, evaluate, and download common purchasable CAD parts from step.parts, including named off-the-shelf actuators, servos, motors, electronics boards, connectors, screws, bolts, nuts, washers, bearings, standoffs, and other catalog components. Use when Codex needs to search the hosted step.parts catalog before…
sendcutsend
Review DXF and STEP/STP uploads for SendCutSend.com orders using its ordering guide, catalog, and specs. Use only for SendCutSend.com preflight reports covering upload readiness, selected material/SKU/thickness/service availability, and service-specific checks for laser cutting, CNC routing, bending, tapping…