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 skills add dartsim/dart --skill dart-changeloggit 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/skills/dartsim/dart/dart-changelog)<a href="https://agentmods.dev/skills/dartsim/dart/dart-changelog"><img src="https://agentmods.dev/badge/skills/dartsim/dart/dart-changelog/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/skills/dartsim/dart/dart-changelog"><img src="https://agentmods.dev/badge/skills/dartsim/dart/dart-changelog.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00024 | $0.02202 |
| Opus 5.5 | $0.00010 | $0.00881 |
| Sonnet 5.5 | $0.00005 | $0.00440 |
| Haiku 4.5 | $0.00002 | $0.00220 |
Grade A, and why
dart-changelog 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.
How it starts
The opening of the file, as written. The whole thing — 202 lines — stays where its author put it; the contents beside it link to each section on GitHub.
dart-changelog
Use this skill to run the DART dart-changelog workflow. The editable workflow
source lives in .claude/commands/; this generated skill is its entrypoint for
Codex and Muse.
Invocation
- Claude Code:
/dart-changelog <arguments> - Codex:
$dart-changelog <arguments> - Muse:
/dart-changelog <arguments>
Treat the text after the skill name, or the user's request when the skill is
loaded on demand, as $ARGUMENTS. When the workflow references $1, $2,
etc., map those to the positional values supplied by the user.
Command Body
Maintain DART changelog entries: $ARGUMENTS
Purpose
dart-changelog is the reusable changelog decision and writing routine. It is
usually invoked by other DART workflows when they reach a changelog decision,
not directly by users.
Use it to:
- decide whether a change needs a changelog entry;
- draft an entry at the right level of detail;
- add a PR link after publication;
- audit pending fragments or a release section for missing or over-detailed entries; or
- assemble
main's fragments at a checkpoint.
On main, an entry is a
changelog.d/ fragment and only checkpoint assembly adds entries to
CHANGELOG.md;
release-* branches edit CHANGELOG.md directly. Keep style, placement,
evidence, and release-note density aligned with docs/onboarding/changelog.md.
Required Reading
@AGENTS.md @docs/onboarding/changelog.md @docs/onboarding/release-management.md @changelog.d/README.md
Modes
Interpret $ARGUMENTS as one of these modes when present:
decide: determine whether the current change needs a changelog entry and record the reason in author/task notes when no entry is needed.draft: write or revise the entry before a PR number exists: achangelog.d/<topic>.mdfragment onmain, aCHANGELOG.mdentry on arelease-*branch.finalize: add the PR link line to the fragment (or release-branch entry) or adjust the entry after a PR exists, keeping the follow-up local until explicit maintainer/user approval permits a push.audit: scan pendingchangelog.d/fragments, aCHANGELOG.mdrelease section, or a PR set for missing, duplicate, over-detailed, misplaced, or stale entries.release-audit: alias forauditwhen the caller is finalizing a release section as part of release packaging (seedocs/onboarding/release-management.md).assemble: at a checkpoint (each milestone exit, before a release candidate, tag, or release-branch cut frommain, or when the maintainer asks), runpixi run changelog-assembleon a topic branch from freshorigin/main, thenrelease-auditthe assembled section. Its PR still needs explicit maintainer/user approval before it is opened.
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 Changed · +6 lines e0a73f2bcf72
- 6d ago Changed · +26 lines · +2 tokens per session 913579064efe
- 16d ago Changed · +2 lines 8403e742a6f1
- 19d ago Changed 09cf7e081f9b
- 20d ago Changed · +3 lines 91772a062f5d
- 24d ago Changed b24f40bd75b9
- 1mo ago Changed · +4 lines a7bcb6986d8b
- 1mo ago Changed 35734e7f3235
- 1mo ago First seen · 161 lines · 22 tokens per session scan A d2d025caabf2
dart-changelog is a skill published in the GitHub repository dartsim/dart (1,222 stars, last pushed yesterday), licensed BSD-2-Clause. It adds 24 tokens to every session and 2,202 once invoked, about $0.0001 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 skills, from other repositories
release-announcement
Write a release announcement — changelog, blog post, in-app note, or social post — that leads with user impact, names the audience, and includes upgrade/migration steps without filler.
release
Fully automate a release with version-bump and childhood.
release-notes
Generate user-facing release notes from tickets, PRDs, or changelogs. Creates clear, engaging summaries organized by category (new features, improvements, fixes). Use when writing release notes, creating changelogs, announcing product updates, or summarizing what shipped.
multi-agent-release-manager
Cleans up the workspace, formats code, runs presubmit checks, and uploads CLs to Gerrit.
pack-submit
Package one of this agent's own skills as a standalone community pack and submit it to the aeon registry as a PR.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.