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-benchmark-packet.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-benchmark-packet)<a href="https://agentmods.dev/commands/dartsim/dart/dart-benchmark-packet"><img src="https://agentmods.dev/badge/commands/dartsim/dart/dart-benchmark-packet.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.1 | $0.00011 | $0.00347 |
| Opus 5 | $0.00005 | $0.00173 |
| Sonnet 5 | $0.00002 | $0.00069 |
| Haiku 4.5 | $0.00001 | $0.00035 |
Grade A, and why
dart-benchmark-packet 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 5d 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
Author or refresh a benchmark evidence packet: $ARGUMENTS
Required Reading
@AGENTS.md @docs/onboarding/profiling.md
Also read the owning plan file named by the packet (for example
docs/plans/<NNN>-<slug>.md) and its packet convention.
Workflow
- Identify the owning plan and its packet convention: the packet checker (for
example
pixi run check-avbd-packets) and the packet generator (for examplescripts/write_*_packet.py) that the plan names. - Build the benchmark target and run the benchmark that feeds the packet,
following
docs/onboarding/profiling.mdfor a stable measurement setup. - Run the packet writer to record the machine-generated evidence packet with its provenance and resolved configuration.
- Validate the packet with the plan's packet checker; treat a failing checker as incomplete evidence and fix the packet, not the checker.
- Prepare the owning plan's row or link update that task-specific gates require, but leave editing the plan file to the plan's own workflow — this command prepares and validates the packet. This is a local task; do not push or open PRs without explicit maintainer/user approval.
Output
- Owning plan, packet ID, and the checker/generator used
- Benchmark command run and the measurement setup
- Packet file written and checker result
- Whether the packet is new or refreshed, and any remaining gap
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.
- 5d ago First seen · 39 lines · 11 tokens per session scan A f456a7e48886
dart-benchmark-packet 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 347 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
notify
Send a notification to your device.
simulation-commands
Commands for initiating, configuring, and reviewing board simulation sessions -- adversarial role-play rehearsals where the AI assumes board member personas and challenges the entrepreneur's presentations.
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.
status
Show Bubbaloop daemon and node health summary.