dart-pr

dart-pr is a skill for Claude Code from dartsim/dart. It costs 22 tokens per session (1,839 once invoked), scanned A, original, BSD-2-Clause.

A workflow for preparing a DART pull request by creating a branch, committing changes, pushing them, and opening the request.

In plain words
What is it for?
Reading contribution guidance, checking recent pull-request patterns, drafting the request, and publishing it after approval.
Why use it?
It provides a consistent path from local code changes to a reviewable pull request and includes the project's required documentation.

Skill for Claude Code

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

Needs its repository: it runs a file that does not travel with it, so clone the repository first. The line is printf '%s\n' "$pr_title" | pixi run python scripts/check_local_paths.py --stdin.

Good fit Reading contribution guidance, checking recent pull-request patterns, drafting the request, and publishing it after approval.

Compare 6 skills from other repositories ↓
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,223 stars · on GitHub · dart.readthedocs.io

Install

Getting it into your agent

It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.

Clone the repo
git clone --depth 1 https://github.com/dartsim/dart
agentmods
npx agentmods add skills/dartsim/dart/dart-pr

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-pr

README.md
[![agentmods](https://agentmods.dev/badge/skills/dartsim/dart/dart-pr/github.svg)](https://agentmods.dev/skills/dartsim/dart/dart-pr)
Your own site
<a href="https://agentmods.dev/skills/dartsim/dart/dart-pr"><img src="https://agentmods.dev/badge/skills/dartsim/dart/dart-pr/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.

agentmods 80×15 button for dart-pr

Your own site · 80×15
<a href="https://agentmods.dev/skills/dartsim/dart/dart-pr"><img src="https://agentmods.dev/badge/skills/dartsim/dart/dart-pr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 22 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,839 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.00022 $0.01839
Opus 5.5 $0.00009 $0.00736
Sonnet 5.5 $0.00004 $0.00368
Haiku 4.5 $0.00002 $0.00184

Measured 23d ago against content hash c220dab8473b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

dart-pr 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 23d 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.

.agents/skills/dart-pr/SKILL.md · 176 lines

How it starts

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

dart-pr

Use this skill to run the DART dart-pr workflow. The editable workflow source lives in .claude/commands/; this generated skill is its entrypoint for Codex and Muse.

Invocation

  • Claude Code: /dart-pr <arguments>
  • Codex: $dart-pr <arguments>
  • Muse: /dart-pr <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

Prepare or open a DART pull request after explicit maintainer/user approval: $ARGUMENTS

Required Reading

@AGENTS.md @docs/onboarding/contributing.md @docs/onboarding/release-management.md @docs/onboarding/ai-tools.md @docs/onboarding/changelog.md @.github/PULL_REQUEST_TEMPLATE.md

Recent PR Patterns

When project context is unclear, inspect recently merged PRs for examples; the current PR-description owner below takes precedence over older bodies:

gh pr list --repo dartsim/dart --state merged --base <target-branch> --limit 10 \
  --json number,title,body,mergedAt

Use these practices:

  • Keep titles plain, scoped, and outcome-focused. Do not add agent prefixes.
  • Describe private plans in prose or link public PRs/issues. Keep private, local, and machine-specific paths out of the title and body.
  • Follow docs/onboarding/contributing.md § "PR Descriptions" for the Summary and Testing default, optional material context, evidence formats, and collapsed detail. This is the PR-description owner for agents and contributors. Write each paragraph and list item of the body on one line: GitHub renders newlines as line breaks, so never wrap PR text at a fixed width.
  • For CI, performance, or infrastructure work, include evidence that supports the outcome and relevant verification gaps.
  • For model/scene, dynamics, collision/contact, simulation, rendering, mesh, texture, GUI, or visual-example changes, use dart-verify-sim: report the text correctness oracle and include assessed, claim-tied Filament/debug-overlay evidence when applicable (an image alone is not correctness proof):
    • Prefer an existing headless example path such as --headless, --frames, --width, --height, and --shot over manual screenshots.
    • Follow docs/ai/verification.md § "Simulation Verification Route" for before/after 3D highlights, matched captures, and compute-only plots.
    • Inspect the images yourself and retain reproduction commands and environment details in collapsed evidence details. Keep limiting caveats and failed or uncertain results prominent.
    • Use pixi run evidence-publish to render the section without network access. Follow docs/ai/verification.md § "Visual Verification (Headless Capture)" for publication after explicit maintainer/user approval. Attachments use the same store as drag-and-drop, never release assets or tags; --body-file replaces the whole PR body. Keep transient PR evidence out of Git; commit visual files only as durable documentation, fixtures, or source assets.
    • If no headless path exists, either add a narrowly scoped capture mode when it fits the example or document why visual comparison is not practical.
  • Link relevant PRs, issues, backports, and follow-ups when useful to the review.

Read the full file on GitHub · 176 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. 23d ago Changed · +2 lines c220dab8473b
  2. 25d ago Changed · -11 lines f5c2c1f83969
  3. 26d ago Changed · +4 lines 1b830cc83376
  4. 28d ago Changed · -33 lines e6392614c2cf
  5. 29d ago Changed · -3 lines 17591ed6d406
  6. 1mo ago Changed · +1 lines 6956aa9bc0cf
  7. 1mo ago Changed · +93 lines 540c0666c253
  8. 2mo ago Changed · -14 lines c949530ed8fa
  9. 2mo ago Changed · -17 lines 1bdd7b561cf7
  10. 2mo ago First seen · 154 lines · 22 tokens per session scan A 0ea55b614c60

Subscribe to this mod's changes

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

Related

dart-pr compared with skills from other repositories

dart-pr next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
dart-prdartsim/dartSkill1.2kyesterdayBSD-2-ClauseA22Claude Code
review-deltatirth8205/code-review-graphSkill33k8d agoMITA24Claude Code
hero-diff-highlightUnclecheng-li/AI_AnimationSkill1.7k11d agoMITA0Claude Code, Codex
lean-reviewSnowflake-Labs/cocoplusSkill7272d agoMITA44Claude Code
git-pr-workflows-git-workflowrmyndharis/antigravity-skillsSkill1.9k23d agoMITA37Claude Code
review-gatemajiayu000/spellbookSkill2902d agoMITA95Claude Code, Codex
dyl-reviewcursor/pluginsSkill15kyesterdaynoneA80Claude Code, Cursor