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-close-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-close-issue)<a href="https://agentmods.dev/commands/dartsim/dart/dart-close-issue"><img src="https://agentmods.dev/badge/commands/dartsim/dart/dart-close-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.00010 | $0.00228 |
| Opus 5 | $0.00005 | $0.00114 |
| Sonnet 5 | $0.00002 | $0.00046 |
| Haiku 4.5 | $0.00001 | $0.00023 |
Grade A, and why
dart-close-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 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.
What it actually says
Close or prepare closing message for issue: $ARGUMENTS
Required Reading
@AGENTS.md @docs/onboarding/contributing.md
Workflow
- Inspect the issue:
gh issue view <ISSUE_NUMBER> --comments. - Verify the stated resolution:
- fixed by merged PR
- already fixed on
main - no longer reproducible
- out of scope or needs a different tracker
- Draft a concise closing message:
- thank the reporter
- state the concrete resolution
- link the fixing PR or relevant docs when available
- Only post and close if the user explicitly requested action and explicit
maintainer/user approval has been given:
gh issue comment <ISSUE_NUMBER> --body "<message>" gh issue close <ISSUE_NUMBER>
Output
- Closing message
- Whether it was posted
- Whether the issue was closed
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 First seen · 38 lines · 10 tokens per session scan A e446c35baef0
dart-close-issue is a command published in the GitHub repository dartsim/dart (1,201 stars, last pushed today), licensed BSD-2-Clause. It adds 10 tokens to every session and 228 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
commit-message
Suggest a clear and simple commit message for the current changes.
simplify-comments
Review the comments in a given range and cut them down to only what is needed.
notify
Send a notification to your device.
stream
Get the Zenoh topic and connection params for a node's data stream.
node-new
Scaffold a new bubbaloop node via the bubbaloop-node-author subagent — guided through manifest, command queryable, validation, and registration.
diagnose
Diagnose a node — health, manifest, logs, recommended action.