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-fix-issuegit 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-fix-issue)<a href="https://agentmods.dev/commands/dartsim/dart/dart-fix-issue"><img src="https://agentmods.dev/badge/commands/dartsim/dart/dart-fix-issue.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.00011 | $0.00457 |
| Opus 5 | $0.00005 | $0.00229 |
| Sonnet 5 | $0.00002 | $0.00091 |
| Haiku 4.5 | $0.00001 | $0.00046 |
Grade A, and why
dart-fix-issue 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 yesterday.
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
Fix GitHub issue: $ARGUMENTS
Required Reading
@AGENTS.md @docs/onboarding/contributing.md @docs/onboarding/changelog.md @docs/ai/verification.md
Workflow
If the fix depends on 3D structure or behavior, route through
dart-verify-sim: text oracle plus assessed visual evidence, or a recorded
exception.
gh issue view $1- Validate issue- Classify whether the issue is a bug fix that applies to the active DART 6
LTS branch. For applicable bug fixes, start from the highest maintained
origin/release-6.*branch; otherwise start fromorigin/main. - Fix with minimal changes + add regression test. For dual-PR bug fixes, fix
the active DART 6 LTS branch first, then cherry-pick or reapply to
main. pixi run lint, then the smallest relevant tests and the task-type gate set fromdocs/ai/verification.md- Before PR creation, invoke the
dart-changelogroutine to decide whetherCHANGELOG.mdneeds an entry, then fill.github/PULL_REQUEST_TEMPLATE.md. - After explicit maintainer/user approval,
git push -u origin HEAD && gh pr create --base <target-branch> --milestone "<milestone>" - Before PR: If task used
docs/dev_tasks/<task>/, remove the folder (include in this PR, not after merge)
CRITICAL: Dual-PR for Bug Fixes
PRs to BOTH the active DART 6 LTS branch AND main. See
docs/onboarding/contributing.md.
Output
- Issue number and classification (bug fix, dual-PR, or main-only)
- Fix summary and regression test added
- Gates run (lint, focused tests,
pixi run test-all) - PR readiness for each target branch, noting any explicitly approved mutation
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.
- yesterday Changed · -3 lines 3adc148e46cb
- 3d ago First seen · 49 lines · 11 tokens per session scan A 219904ac329e
dart-fix-issue is a command published in the GitHub repository dartsim/dart (1,201 stars, last pushed yesterday), licensed BSD-2-Clause. It adds 11 tokens to every session and 457 once invoked, about $0.0001 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
write-tests
Generate comprehensive test coverage for existing code.
test-tdd
Run when user calls /test-tdd. Scans modified files, locates their corresponding unit/integration test suites, and runs them.
test
Generate comprehensive tests.
pr-enhance
Command "pr-enhance" from ruvnet/ruflo, covering pr-enhance, usage, options, examples and enhance pr.
unit-test
Write / run the unit tests for the feature. (AIDLC Unit Test phase) Usage: /unit-test.
test
Execute a comprehensive test run for the following target.