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.
git 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/commands/dartsim/dart/dart-release-ci-fix)<a href="https://agentmods.dev/commands/dartsim/dart/dart-release-ci-fix"><img src="https://agentmods.dev/badge/commands/dartsim/dart/dart-release-ci-fix/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/commands/dartsim/dart/dart-release-ci-fix"><img src="https://agentmods.dev/badge/commands/dartsim/dart/dart-release-ci-fix.svg" alt="Reviewed on agentmods" width="80" 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.00012 | $0.00622 |
| Opus 5.5 | $0.00005 | $0.00249 |
| Sonnet 5.5 | $0.00002 | $0.00124 |
| Haiku 4.5 | $0.00001 | $0.00062 |
Grade A, and why
dart-release-ci-fix 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 4d 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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Fix DART CI: $ARGUMENTS
Required Reading
@AGENTS.md @docs/onboarding/ci-cd.md @docs/onboarding/release-management.md
Workflow
For a failure involving model/scene structure, physics behavior, or Filament output,
use dart-verify-sim to reproduce the claim with text and assessed visual
evidence. Document a visual exception when graphics support is unavailable or not
applicable.
- Inspect the failing run:
gh run view <RUN_ID> --log-failed gh run view <RUN_ID> --job <JOB_ID> --log - Resolve the target from the live PR base or failing run's branch.
Default to
mainwhen no target is specified. Fetch that target and read itsdocs/onboarding/release-management.md§ "Release target"; verify the exactDART <Next release>milestone is open on GitHub. Publishing requires explicit maintainer/user approval. - If continuing an existing PR, fetch and checkout that branch. Otherwise
branch from the resolved target branch without resetting an existing local
branch:
TARGET_BRANCH=${TARGET_BRANCH:-main} git fetch origin "$TARGET_BRANCH" BRANCH=fix/<issue>-${TARGET_BRANCH} if git show-ref --verify --quiet "refs/heads/$BRANCH"; then git switch "$BRANCH" else git switch --no-track -c "$BRANCH" "origin/$TARGET_BRANCH" fi - If a proven fix exists in a named reference, adapt it only when its
assumptions exist here; otherwise make the smallest branch-scoped fix.
Follow the resolved branch's compatibility rules in
AGENTS.md, preserving C++17, its dartpy binder and GUI backend (nanobind and Filament onmainand DART 7 release branches; pybind11 and OSG onrelease-6.20),dart::utils, and downstream Gazebo/gz-physics behavior. - Explain why the failure was not caught earlier and whether workflow coverage should change.
- Run
pixi run lintand release-relevant build/tests. - Ask for explicit maintainer/user approval before pushing, creating, or
updating the PR. After approval, push to the existing PR when step 3
continued one; otherwise open a new draft PR with the resolved next-release
milestone and PR template. Then follow
docs/onboarding/ai-tools.md§ "PR Lifecycle". - Monitor CI until green.
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.
- 4d ago Changed · +2 lines · -2 tokens per session a8b62ccf3656
- 6d ago Changed · +3 lines · -1 tokens per session d29391f9a0dc
- 9d ago Changed · +2 lines 7da69795f230
- 11d ago Changed · +1 lines adb2365e0854
- 17d ago First seen · 59 lines · 15 tokens per session scan A 25c2c08ad48d
dart-release-ci-fix is a command published in the GitHub repository dartsim/dart (1,217 stars, last pushed today), licensed BSD-2-Clause. It adds 12 tokens to every session and 622 once invoked, about $0.0000 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-09-30.
Other commands, from other repositories
ci-debug
Diagnose a failing CI run against an 11-pattern playbook. Classifies the failure, cites the relevant memory entry, proposes the exact fix command — but NEVER applies without explicit user approval. Use when a specific PR check or GitHub Actions run failed and you want a diagnosis instead of speculation. Don't use for…
metrics
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
traces
Apply the CLI runtime and safety contract before executing a command. Runtime --help is authoritative.
add-debug-wait
Add a wait step to a CI workflow for debugging test failures.
pr-quality-gate-reliability
You are reviewing a pull request for production survivability: how the change behaves when its dependencies misbehave, time out, or fail.
fix-ci
Find failing PR checks, inspect logs or check links, and apply focused fixes. Routing depends on failure type (build/test/security). Usage: /fix-ci [branch|PR].