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.
Borrowing it
Nothing to install: this file belongs to dartsim/dart. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/dartsim/dart/main/.agents/skills/dart-ultrawork/SKILL.mdgit 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-ultrawork)<a href="https://agentmods.dev/skills/dartsim/dart/dart-ultrawork"><img src="https://agentmods.dev/badge/skills/dartsim/dart/dart-ultrawork/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.
<a href="https://agentmods.dev/skills/dartsim/dart/dart-ultrawork"><img src="https://agentmods.dev/badge/skills/dartsim/dart/dart-ultrawork.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00035 | $0.02243 |
| Opus 5 | $0.00017 | $0.01122 |
| Sonnet 5 | $0.00007 | $0.00449 |
| Haiku 4.5 | $0.00003 | $0.00224 |
Grade A, and why
dart-ultrawork 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 2d 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.
How it starts
The opening of the file, as written. The whole thing — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.
dart-ultrawork
Use this skill in Codex to run the DART dart-ultrawork workflow. The editable
workflow source lives in .claude/commands/; this file is its generated adapter
in the shared .agents/skills/ catalog.
Invocation
- Claude Code:
/dart-ultrawork <arguments> - Codex:
$dart-ultrawork <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
Start a team-scale or autonomous DART task: $ARGUMENTS
Required Reading
@AGENTS.md @docs/ai/principles.md @docs/ai/north-star.md @docs/ai/orchestration.md @docs/dev_tasks/README.md @docs/ai/verification.md
Load additional owners only when the matching phase needs them:
- placement or cleanup:
docs/README.md; - numbered-plan selection or packet state:
docs/plans/dashboard.md; - version control, changelog, tools, or review:
docs/onboarding/{contributing,changelog,ai-tools}.md.
Arguments
$ARGUMENTS is a task brief plus optional mode flags:
mode=interview: ask one up-front batch of critical questions.mode=brief: treat provided context as sufficient unless escalation applies.mode=resume: start from the existingdocs/dev_tasks/<task>/project home and run the session-start protocol before changing files.interview=skip: skip maintainer questions only when the brief already answers all consequential decisions.
The brief may be prose or a structured TASK / CONTEXT block. Extract north
star, deliverable, acceptance criteria, constraints, risks, references, paths,
issues/PRs/branches, commands, and first step when present.
Workflow
Own understanding, decomposition, sequencing, review, and honest evidence for
the whole task. Follow the orchestrator/executor and packet-sizing contracts in
docs/ai/orchestration.md. Delegate only when the user explicitly requested it
and the current surface permits it; otherwise execute packets serially. Use
dart-new-task for bounded single-session work unless the user asked for the
autonomous project-home loop.
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.
- 2d ago Changed · +2 lines f102557b1255
- 4d ago Changed · -6 lines 8b0810e5b3d6
- 5d ago Changed · +1 lines 1c397dd30921
- 8d ago First seen · 190 lines · 35 tokens per session scan A 9a2208c083be
dart-ultrawork is a skill published in the GitHub repository dartsim/dart (1,204 stars, last pushed 2d ago), licensed BSD-2-Clause. It adds 35 tokens to every session and 2,243 once invoked, about $0.0002 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.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
remove
Remove a deployed framework or addon from the current workspace.
magpie-security-issue-import-from-md
Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.