dart: Skill for Claude Code

.agents/skills/dart-release-packaging/SKILL.md

dart-release-packaging is a skill for Claude Code from dartsim/dart. It costs 19 tokens per session (523 once invoked), scanned A, original, BSD-2-Clause.

A workflow for preparing a software release pull request by changing version numbers and updating the changelog. A changelog records notable changes in each release.

In plain words
What is it for?
Use it to create a release branch, update package versions, review changelog entries, run checks, and prepare a pull request.
Why use it?
It gathers the version, branch, documentation, checks, and approval steps needed for a consistent release preparation process.

Skill for Claude Code

Written for Claude Code: $ARGUMENTS substitution. Also seen: reads .claude/ paths; positional $N argument; mentions Claude Code.

This is dartsim/dart's own configuration. It tells Claude Code how to work on dart itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything dart configures →

About the project

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.

dartsim/dart · 1,202 stars · on GitHub · dart.readthedocs.io

Reuse

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.

Copy the file
curl -O https://raw.githubusercontent.com/dartsim/dart/main/.agents/skills/dart-release-packaging/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/dartsim/dart

Made for: Claude Code.

Wrote 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.

agentmods badge for dart-release-packaging

README.md
[![agentmods](https://agentmods.dev/badge/skills/dartsim/dart/dart-release-packaging.svg)](https://agentmods.dev/skills/dartsim/dart/dart-release-packaging)
Your own site
<a href="https://agentmods.dev/skills/dartsim/dart/dart-release-packaging"><img src="https://agentmods.dev/badge/skills/dartsim/dart/dart-release-packaging.svg" alt="Measured on agentmods" height="20"></a>
Per session 19 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 523 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector pass 7 Sept 2026
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00019 $0.00523
Opus 5 $0.00010 $0.00262
Sonnet 5 $0.00004 $0.00105
Haiku 4.5 $0.00002 $0.00052

Measured today against content hash f7b1d407f207, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

dart-release-packaging 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 today.

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.

.agents/skills/dart-release-packaging/SKILL.md · 65 lines

How it starts

The opening of the file, as written. The whole thing — 65 lines — stays where its author put it; the contents beside it link to each section on GitHub.

dart-release-packaging

Use this skill in Codex to run the DART dart-release-packaging workflow. The editable workflow source lives in .claude/commands/; this file is its generated adapter in the shared .agents/skills/ catalog.

Invocation

  • Claude Code: /dart-release-packaging <arguments>
  • Codex: $dart-release-packaging <arguments>

Treat the text after the skill name as $ARGUMENTS. When the workflow references $1, $2, etc., map those to the positional values supplied by the user.

Command Body

Create release packaging PR after explicit maintainer/user approval: $ARGUMENTS

Required Reading

@AGENTS.md @docs/onboarding/release-management.md @docs/onboarding/contributing.md @docs/onboarding/changelog.md

Workflow

  1. Confirm the new version, for example 6.16.6.
  2. Derive the release branch: release-<major>.<minor>.
  3. Fetch and branch from the release branch:
    git fetch origin <RELEASE_BRANCH>
    git checkout -B release/<NEW_VERSION>-version-bump origin/<RELEASE_BRANCH>
    
  4. Bump versions in package.xml and pixi.toml.
  5. Update version requirements in examples/tutorials if needed.
  6. Invoke the dart-changelog routine in release-audit mode, then add or finalize the CHANGELOG.md release section with the release date, milestone link, release summary, and audit from docs/onboarding/changelog.md.
  7. Run pixi run lint and relevant packaging checks.
  8. Commit as Packaging <NEW_VERSION>.
  9. Ask for explicit maintainer/user approval before pushing, creating the PR, or setting milestones.
  10. After approval, create the PR against the release branch with the release milestone for that branch, for example the specific version milestone if available.

Output

  • PR URL
  • Version files changed
  • Changelog section added
  • Checks run

Read the full file on GitHub · 65 lines

Changes

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.

  1. today Changed f7b1d407f207
  2. 6d ago First seen · 65 lines · 19 tokens per session scan A d58d486d6d18

Subscribe to this mod's changes

dart-release-packaging is a skill published in the GitHub repository dartsim/dart (1,202 stars, last pushed yesterday), licensed BSD-2-Clause. It adds 19 tokens to every session and 523 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.