dart-new-task

dart-new-task is a command for Claude Code from dartsim/dart. It costs 17 tokens per session (845 once invoked), scanned A, original, BSD-2-Clause.

A DART workflow for starting a feature, bug fix, refactor, documentation, build, or test task.

In plain words
What is it for?
Use it to set up ordinary development tasks or document larger, multi-session, public-API, release, or cross-module work.
Why use it?
It provides a structured intake for task scope, assumptions, acceptance evidence, and decisions before code changes begin.

Command for 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

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 commands/dartsim/dart/dart-new-task
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-new-task

README.md
[![agentmods](https://agentmods.dev/badge/commands/dartsim/dart/dart-new-task.svg)](https://agentmods.dev/commands/dartsim/dart/dart-new-task)
Your own site
<a href="https://agentmods.dev/commands/dartsim/dart/dart-new-task"><img src="https://agentmods.dev/badge/commands/dartsim/dart/dart-new-task.svg" alt="Measured on agentmods" height="20"></a>
Per session 17 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 845 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 $0.00017 $0.00845
Opus 5 $0.00009 $0.00423
Sonnet 5 $0.00003 $0.00169
Haiku 4.5 $0.00002 $0.00085

Measured yesterday against content hash c80807e55850, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

dart-new-task 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 yesterday.

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.

.claude/commands/dart-new-task.md · 73 lines

How it starts

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

Start a new task in DART: $ARGUMENTS

Required Reading

Read these files first: @AGENTS.md @docs/onboarding/building.md @docs/onboarding/contributing.md @docs/onboarding/code-style.md @docs/dev_tasks/README.md @docs/information-architecture.md @docs/ai/sessions.md @docs/ai/principles.md @docs/ai/verification.md

Workflow

  1. Understand the task - Parse: goal, constraints, type (feature|bugfix|refactor|docs)
  2. Assess scope - Multi-phase or multi-session? Create docs/dev_tasks/<task>/ (see docs/dev_tasks/README.md for criteria). Team-scale work (multiple parallel lanes needing orchestrated worker agents) switches to dart-ultrawork instead. For multi-session, design-heavy, public API, solver/paper, release, or cross-module work, fill the dev-task specification intake before editing: value, scope, assumptions, traceability, non-goals, acceptance evidence, gates, and open decisions. If consequential ambiguity would change public API, release compatibility, numerical correctness, benchmark claims, or roadmap scope, record an owner-local Decision needed block instead of silently choosing.
  3. Setup - Choose the target branch before creating a topic branch:
    • features/docs/non-bugfix refactors: branch from origin/main
    • bug fixes that apply to the current release line: branch from the active DART 6 LTS origin/release-6.* branch first, then cherry-pick or reapply to main
  4. Implement - Keep commits focused, follow code style
  5. Verify - Run pixi run lint before committing, then the gate set for this task type from docs/ai/verification.md. If the claim depends on 3D structure or behavior, route through dart-verify-sim: text oracle first, then assessed claim-tied visual evidence, or record why it is not applicable.
  6. PR - After explicit maintainer/user approval, git push -u origin HEAD then gh pr create --draft --base <target-branch> --milestone "<milestone>" (DART 7.0 for main, branch-matching DART 6.x release milestone for the active DART 6 LTS branch); follow .github/PULL_REQUEST_TEMPLATE.md
  7. Cleanup - Before PR: if task used docs/dev_tasks/<task>/, first promote durable dashboards, evidence matrices, API inventories, migration maps, or long-lived decisions into the durable owner selected by docs/information-architecture.md. Then remove the dev-task folder completely (include the deletion in this PR, not after merge).

Read the full file on GitHub · 73 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. yesterday Changed · -14 lines c80807e55850
  2. 3d ago First seen · 87 lines · 17 tokens per session scan A becb15d0b2a6

Subscribe to this mod's changes

dart-new-task is a command published in the GitHub repository dartsim/dart (1,201 stars, last pushed yesterday), licensed BSD-2-Clause. It adds 17 tokens to every session and 845 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.