dart-plan-update

dart-plan-update is a skill for Claude Code from dartsim/dart. It costs 16 tokens per session (882 once invoked), scanned A, original, BSD-2-Clause.

A workflow for discussing or updating DART’s living development plans.

In plain words
What is it for?
Use it to compare planning options, revise plan documents, or turn a plan item into a bounded implementation or documentation task.
Why use it?
It requires checking current project evidence before changing priorities, scope, sequencing, or plan status.

Skill for Claude Code

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

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,201 stars · on GitHub · dart.readthedocs.io

Install

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.

agentmods
npx agentmods add skills/dartsim/dart/dart-plan-update
Any agent
npx skills add dartsim/dart --skill dart-plan-update
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-plan-update

README.md
[![agentmods](https://agentmods.dev/badge/skills/dartsim/dart/dart-plan-update.svg)](https://agentmods.dev/skills/dartsim/dart/dart-plan-update)
Your own site
<a href="https://agentmods.dev/skills/dartsim/dart/dart-plan-update"><img src="https://agentmods.dev/badge/skills/dartsim/dart/dart-plan-update.svg" alt="Measured on agentmods" height="20"></a>
Per session 16 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 882 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
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.00016 $0.00882
Opus 5 $0.00008 $0.00441
Sonnet 5 $0.00003 $0.00176
Haiku 4.5 $0.00002 $0.00088

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

Security

Grade A, and why

dart-plan-update 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-plan-update/SKILL.md · 91 lines

How it starts

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

dart-plan-update

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

Invocation

  • Claude Code/OpenCode: /dart-plan-update <arguments>
  • Codex: $dart-plan-update <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

Discuss or update DART living plans: $ARGUMENTS

Required Reading

@AGENTS.md @docs/ai/principles.md @docs/ai/README.md @docs/ai/orchestration.md @docs/ai/north-star.md @docs/plans/README.md @docs/plans/dashboard.md @docs/plans/north-star-roadmap.md @docs/ai/verification.md

Workflow

  1. Classify the request:
    • discussion-only: compare options, priority, scope, or sequencing;
    • plan edit: revise docs/plans/** or related indexes;
    • task derivation: turn a plan item into a bounded implementation or docs task.
  2. Inspect current evidence before changing plan state. Use repo docs, code, tests, CI evidence, issue/PR state, benchmark data, or explicit maintainer direction.
    • For solver/paper implementation plans, hold the plan to docs/ai/verification.md § "Research Paper Implementation Evidence", record the completed slice and the next missing paper-parity gap, and keep the corpus matrix (tests, py-demos, visual artifacts, benchmark JSON, CPU reference comparisons, GPU parity) explicit about missing rows.
  3. Keep the plan manageable:
    • revise an existing initiative before adding a duplicate;
    • use stable initiative IDs when renaming, splitting, consolidating, or parking work;
    • keep docs/plans/dashboard.md as the single source of truth for priority, status, horizon, dimension, next step, and gate.
    • when deriving packets or dev-task work, include the DART specification intake from docs/ai/orchestration.md: value, scope, non-goals, assumptions/open decisions (including reasoning mode, phase, and approved delegation scopes), acceptance evidence, gates, and dependencies. Use owner-local Decision needed blocks for consequential ambiguity instead of silent defaults.
  4. For discussion-only requests, present the tradeoff and proposed plan delta; do not edit unless the user asks for an edit or the request already implies one.
  5. For plan edits, update docs/plans/dashboard.md for operating state, the detailed numbered initiative file or external owner document for rationale and workstreams, and docs/plans/north-star-roadmap.md only for strategic framing.
  6. If the plan item becomes implementation work, route to /dart-new-task in Claude/OpenCode or $dart-new-task in Codex, and use docs/dev_tasks/README.md when it is multi-session or needs design tracking.
  7. Verify with docs/ai/verification.md: use the docs-only gate for plan-only docs, and the AI docs/adapters gate set when AI docs, workflow sources, or generated adapters change.
  8. Do not perform GitHub or remote mutations without explicit maintainer/user approval.

Read the full file on GitHub · 91 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 · +3 lines ec3be275d7d9
  2. 2d ago Changed · -6 lines 2e8bf3c23cbf
  3. 4d ago First seen · 94 lines · 16 tokens per session scan A 9e4208a620d5

Subscribe to this mod's changes

dart-plan-update is a skill published in the GitHub repository dartsim/dart (1,201 stars, last pushed today), licensed BSD-2-Clause. It adds 16 tokens to every session and 882 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.

Related

Other skills, from other repositories

evaluating-cosmos-policy

Evaluates NVIDIA Cosmos Policy on LIBERO and RoboCasa simulation environments. Use when setting up cosmos-policy for robot manipulation evaluation, running headless GPU evaluations with EGL rendering, or profiling inference latency on cluster or local GPU machines.

Orchestra-Research/AI-Research-SKILLs · 51 tokens

smui

Local copy of the smui ("spacemolt") design system ( ), adapted for the CAD Viewer. smui is a Nord-inspired terminal aesthetic for shadcn/ui with light and dark modes: sharp edges, monospace everything. Read this whole document before restyling viewer UI.

earthtojake/text-to-cad · 0 tokens

cad-viewer

Start CAD Viewer and return review links for CAD and robot-description files. Use when visually reviewing .step, .stp, .glb, .stl, .3mf, .dxf, .urdf, .srdf, or .sdf files, especially when handed off from CAD, URDF, SRDF, or SDF generation skills.

earthtojake/text-to-cad · 79 tokens

urdf

URDF robot description authoring and validation. Use when creating, editing, inspecting, validating, or debugging .urdf files, robot links, joints, limits, inertials, visual/collision geometry, mesh references, frame conventions, or robot-description artifacts. Use the SRDF skill for MoveIt2 semantic groups and…

earthtojake/text-to-cad · 92 tokens

step-parts

Find, evaluate, and download common purchasable CAD parts from step.parts, including named off-the-shelf actuators, servos, motors, electronics boards, connectors, screws, bolts, nuts, washers, bearings, standoffs, and other catalog components. Use when Codex needs to search the hosted step.parts catalog before…

earthtojake/text-to-cad · 119 tokens

sendcutsend

Review DXF and STEP/STP uploads for SendCutSend.com orders using its ordering guide, catalog, and specs. Use only for SendCutSend.com preflight reports covering upload readiness, selected material/SKU/thickness/service availability, and service-specific checks for laser cutting, CNC routing, bending, tapping…

earthtojake/text-to-cad · 75 tokens