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/.claude/commands/dart-release-merge-main.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/commands/dartsim/dart/dart-release-merge-main)<a href="https://agentmods.dev/commands/dartsim/dart/dart-release-merge-main"><img src="https://agentmods.dev/badge/commands/dartsim/dart/dart-release-merge-main/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-merge-main"><img src="https://agentmods.dev/badge/commands/dartsim/dart/dart-release-merge-main.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.00008 | $0.00366 |
| Opus 5 | $0.00004 | $0.00183 |
| Sonnet 5 | $0.00002 | $0.00073 |
| Haiku 4.5 | $0.00001 | $0.00037 |
Grade A, and why
dart-release-merge-main 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 6d 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
Merge release branch into main: $ARGUMENTS
Required Reading
@AGENTS.md @docs/onboarding/release-management.md @docs/onboarding/ci-cd.md
Workflow
- Auto-detect or confirm the active release branch and release version:
git fetch origin git branch -r | grep -oE 'origin/release-[0-9]+\.[0-9]+' | sort -V | tail -1 - Verify the clone is not shallow and a merge base exists.
- Create
merge/<release-branch>-into-mainfromorigin/main. - Merge the release branch with a title like
Merge release-6.20 into main (v6.20.x). - Resolve conflicts using
docs/onboarding/release-management.md:- deleted in main, updated in release: keep deleted
- added in both: prefer main unless release has unique needed content
- content conflicts: prefer main modernization except for manually reviewed changelog entries
- files only on release: keep if still relevant to main
- Verify no unresolved conflicts remain.
- Run
pixi run lintand relevant checks. - Ask for explicit maintainer/user approval before pushing or creating the PR.
After approval, create a PR targeting
mainwith milestoneDART 7.0and use the PR template. - Monitor CI until green.
Output
- PR URL and CI status
- Release branch and release version
- Conflict counts and resolution summary
- Any manual changelog decisions
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.
- 6d ago Changed 82de4bf2411e
- 9d ago First seen · 44 lines · 8 tokens per session scan A da55c54b7409
dart-release-merge-main is a command published in the GitHub repository dartsim/dart (1,204 stars, last pushed 3d ago), licensed BSD-2-Clause. It adds 8 tokens to every session and 366 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
land
Cadence-tick autonomous PR babysitter (CI-fix, resolve, converge, merge, close, release).
pr
Create a GitHub PR from current branch with unpushed commits — discovers templates, analyzes changes, pushes.
taupr
The Tau Ceti worker loop — one unit of work per round, first that applies: rebase, fix CI, fix findings, review a stalled PR, else author a new one. Authoring checks the source material first, cleans up, and opens the PR; CI reviews it. We only self-review a PR that CI has left unreviewed for an hour.
iteration-drive
Drive the active iteration to completion — Phase 2 Autonomous Execute, Phase 3 iteration-close, Phase 4 Create PR, Phase 5 PR merge-ready loop (prefer babysit/-babysit; optional greploop when repo has it; else CI fallback) until mergeable. Not Done until Phase 5 exit checklist passes.
gsd:ship
Create PR, run review, and prepare for merge after verification passes.
flow
Universal workflow entry point. Use /flow for skill-driven GitHub development. Verbs: start, commit, pr, review, address, merge, resolve, release, status, learn, setup, explain, debug, design, brainstorm, issue.