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-mechanical-refactor)<a href="https://agentmods.dev/commands/dartsim/dart/dart-mechanical-refactor"><img src="https://agentmods.dev/badge/commands/dartsim/dart/dart-mechanical-refactor/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-mechanical-refactor"><img src="https://agentmods.dev/badge/commands/dartsim/dart/dart-mechanical-refactor.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.00302 |
| Opus 5.5 | $0.00003 | $0.00121 |
| Sonnet 5.5 | $0.00002 | $0.00060 |
| Haiku 4.5 | $0.00001 | $0.00030 |
Grade A, and why
dart-mechanical-refactor 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 16d 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
Perform mechanical refactor: $ARGUMENTS
Required Reading
@AGENTS.md @CONTRIBUTING.md @docs/onboarding/code-style.md
Workflow
- Define the exact transformation and scope before editing.
- Create a topic branch from the target branch, for example
git switch --no-track -c refactor/<topic> origin/main. - Prefer scriptable or automated edits when the transformation is repetitive.
- Keep behavior unchanged; do not mix in feature work or cleanup outside scope.
- If reorganizing files, update CMake, pixi tasks, generated indexes, and docs.
- Run focused checks first, then broader checks according to risk:
pixi run lintpixi run buildpixi run testpixi run test-allwhen feasiblepixi run -e gazebo test-gzwhen package, collision, constraint, or downstream Gazebo/gz-physics compatibility could be affected
- Ask for explicit maintainer/user approval before pushing or opening a PR. After approval, open a PR with a clear scope statement and no behavior-change claim unless tested.
Output
- Transformation summary
- Files or areas changed
- Verification run
- Any residual risk
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.
- 16d ago Changed 4d2a85cf0df7
- 22d ago Changed · +3 lines 482a64bd91cf
- 1mo ago Changed · -1 lines c063d9d2836e
- 1mo ago First seen · 38 lines · 8 tokens per session scan A 9a514186e7b5
dart-mechanical-refactor is a command published in the GitHub repository dartsim/dart (1,217 stars, last pushed today), licensed BSD-2-Clause. It adds 8 tokens to every session and 302 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-01.
Other commands, from other repositories
pr
Automated PR code quality review with language-aware analysis and project-specific profiles.
code-improve
Launch autonomous code improvement loop — detects opportunities, applies improvements, creates PRs for review.
pr-enhance
Command "pr-enhance" from ruvnet/ruflo, covering pr-enhance, usage, options, examples and enhance pr.
refactor-sprint
Parallel refactor sprint — fires refactor-cleaner + code-simplifier + type-design-analyzer + tdd-guide simultaneously. Full cleanup in one pass.
quality-check-command
This command performs comprehensive code quality checks. Use it before commits or when implementation is complete.
gsd-quality
Route to the appropriate quality / review skill based on the user's intent. gsd-code-review-fix was absorbed by gsd-code-review --fix in #2790.