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 commands/dartsim/dart/dart-release-packaginggit 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-packaging)<a href="https://agentmods.dev/commands/dartsim/dart/dart-release-packaging"><img src="https://agentmods.dev/badge/commands/dartsim/dart/dart-release-packaging.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 | $0.00009 | $0.00341 |
| Opus 5 | $0.00005 | $0.00170 |
| Sonnet 5 | $0.00002 | $0.00068 |
| Haiku 4.5 | $0.00001 | $0.00034 |
Grade A, and why
dart-release-packaging 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 3d 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.
What it actually says
Create release packaging PR after explicit maintainer/user approval: $ARGUMENTS
Required Reading
@AGENTS.md @docs/onboarding/release-management.md @docs/onboarding/contributing.md @docs/onboarding/changelog.md
Workflow
- Confirm the new version, for example
6.16.6. - Derive the release branch:
release-<major>.<minor>. - Fetch and branch from the release branch:
git fetch origin <RELEASE_BRANCH> git checkout -B release/<NEW_VERSION>-version-bump origin/<RELEASE_BRANCH> - Bump versions in
package.xmlandpixi.toml. - Update version requirements in examples/tutorials if needed.
- Invoke the
dart-changelogroutine in release-audit mode, then add or finalize theCHANGELOG.mdrelease section with the release date, milestone link, release summary, and audit fromdocs/onboarding/changelog.md. - Run
pixi run lintand relevant packaging checks. - Commit as
Packaging <NEW_VERSION>. - Ask for explicit maintainer/user approval before pushing, creating the PR, or setting milestones.
- After approval, create the PR against the release branch with the release milestone for that branch, for example the specific version milestone if available.
Output
- PR URL
- Version files changed
- Changelog section added
- Checks run
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.
- 3d ago First seen · 44 lines · 9 tokens per session scan A 45828c4467be
dart-release-packaging is a command published in the GitHub repository dartsim/dart (1,201 stars, last pushed yesterday), licensed BSD-2-Clause. It adds 9 tokens to every session and 341 once invoked, about $0.0000 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 commands, from other repositories
commit-push-pr
Commit, push, and open a PR.
create-pr
Rebase from the latest origin/main, squash the commits from it, and then create a PR on github with intelligent commit messages based on staged changes. Invoke with /create-pr.
push-and-release
Git pull, resolve conflicts, push, fix hook errors, then release.
land
Cadence-tick autonomous PR babysitter (CI-fix, resolve, converge, merge, close, release).
release
This compatibility command keeps /oh-my-claudecode:release available without loading the full release skill description in every Claude Code session.
release-notes
Generate consistent, well-structured release notes from git history. Triggered on release tags following semver patterns (v..) to produce categorized changelog with breaking changes, features, fixes, and contributor attribution.