dart-test

dart-test is a skill for Claude Code, Codex from dartsim/dart. It costs 18 tokens per session (826 once invoked), scanned A, original, BSD-2-Clause.

A testing guide for the DART project, covering unit tests, integration tests, CI checks, and debugging failures. Unit tests check small pieces of code; integration tests check how pieces work together.

In plain words
What is it for?
Use it to write GoogleTest tests, run Python or full test suites, validate CI, inspect failed CI logs, and check simulation-related behavior.
Why use it?
It gives contributors the project’s expected test commands and helps narrow down failures before submitting a change.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one. Also seen: reads .claude/ paths; installed under .agents/ (shared by several agents).

Good fit Use it to write GoogleTest tests, run Python or full test suites, validate CI, inspect failed CI logs, and check simulation-related behavior.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/dartsim/dart/dart-test
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,218 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.

Any agent
npx skills add dartsim/dart --skill dart-test
Clone the repo
git clone --depth 1 https://github.com/dartsim/dart

Made for: Claude Code, Codex.

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

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

Your own site · 80×15
<a href="https://agentmods.dev/skills/dartsim/dart/dart-test"><img src="https://agentmods.dev/badge/skills/dartsim/dart/dart-test.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 18 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 826 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 warn 7 Sept 2026
SkillSpector: 1 finding, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium Agent Snooping · line 7
    Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.
    Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00018 $0.00826
Opus 5.5 $0.00007 $0.00330
Sonnet 5.5 $0.00004 $0.00165
Haiku 4.5 $0.00002 $0.00083

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

Security

Grade A, and why

dart-test 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 8d 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-test/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 Testing

Load this skill when writing or debugging tests.

Quick Commands

pixi run test         # Quick test run
pixi run test-py      # Python tests
pixi run test-all     # Build defaults and run C++/Python tests
pixi run test-gui     # GUI tests except native-window tests; needs a graphics device
pixi run -e gazebo test-gz # Gazebo/gz-physics compatibility gate

Full Documentation

For complete testing guide: docs/onboarding/testing.md

For CI/CD troubleshooting: docs/onboarding/ci-cd.md

Test Organization

  • Unit tests: tests/unit/
  • Integration tests: tests/integration/
  • Regression tests: tests/regression/ (start from test_Issue000Template.cpp)

Writing Tests

  1. Follow existing patterns in the test directory
  2. Use GoogleTest framework
  3. Name tests descriptively, in the style of the neighboring tests in that file

CI Validation

Before submitting PR:

pixi run lint         # Must pass
pixi run test-all     # Default build plus C++/Python runtime aggregate
pixi run -e gazebo test-gz # Must pass when Gazebo/gz-physics compatibility could be affected

Debugging Test Failures

# Run the smallest existing Pixi test task that covers the failure
pixi run test

# Get CI logs
gh run view <RUN_ID> --log-failed

Simulation And Visual End-to-End Checks

When a failure or change depends on scene structure, dynamics, collision/contact, simulation stepping, Filament output, or a visual example, also load dart-verify-sim. Use its text-first oracle and then an assessed, claim-tied capture through DebugOverlay. Record a concrete no-visual reason only when capture is unavailable or not applicable.

Gotchas

  • pixi run build builds libraries only, NOT every test binary. If you run ctest directly, build the relevant test target first; pixi run build-tests builds the branch test targets.
  • pixi run test-all builds the default CMake ALL graph. The branch config pins BUILD_TESTING=ON, so that graph also runs CTest and pytest. Pair it with pixi run lint; use pixi run test or pixi run test-py for focused reruns and clearer failure attribution.
  • pixi run test, test-py, and test-all build the GUI but skip tests that need a graphics device (CTest label gui-device and the Python GUI rendering tests). Device-free GUI tests remain in the default gates; the gui label covers all GUI tests. GUI, Filament, and dartpy.gui changes also need pixi run test-gui, which selects -L gui -LE filament-native in the same build/<env>/cpp/Release tree. Native-window tests need a desktop session or Xvfb: ctest --test-dir build/<env>/cpp/Release -L filament-native (ctest --test-dir build/<env>/cpp -C Release -L filament-native on Windows).
  • For package, collision, constraint, or dependency changes that could affect downstream users, run pixi run -e gazebo test-gz.

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. 8d ago Changed · +11 lines fab7a354bdf6
  2. 14d ago Changed 3235b1534302
  3. 20d ago Changed · -4 lines 55e4e3b5125f
  4. 1mo ago Changed · -1 lines 4b5f4851bc11
  5. 1mo ago First seen · 85 lines · 18 tokens per session scan A 4805bd2753ac

Subscribe to this mod's changes

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

Other skills, from other repositories

test-master

Generates test files, creates mocking strategies, analyzes code coverage, designs test architectures, and produces test plans and defect reports across functional, performance, and security testing disciplines. Use when writing unit tests, integration tests, or E2E tests; creating test strategies or automation…

Jeffallan/claude-skills · 104 tokens

migrate-xunit-to-xunit-v3

Migrate .NET test projects from xUnit.net v2 to xunit.v3 and fix v3 breaks. Use for package/CPM conversion, OutputType=Exe, preserving the VSTest or MTP runner (including projects currently using YTest.MTP.XUnit2), incompatible TFMs, async void tests, string-to-Type attributes, custom Fact/Theory/BeforeAfterTest…

dotnet/skills · 149 tokens

principle-test-behavior-not-implementation

Apply when you write, change, or keep a test. Assert what the code's users can observe, so that the test fails when that behavior breaks and keeps passing when only the internals change.

michael-denyer/pstack-claude · 50 tokens

mobiai-ios-testing

Use when writing or running tests in an iOS project — unit tests, UI tests, snapshot tests, choosing the right framework.

ArisGuimera/MobiAI-Core · 31 tokens

testing-llm

LLM and AI testing patterns — mock responses, evaluation with DeepEval/RAGAS, structured output validation, and agentic test patterns (generator, healer, planner). Use when testing AI features, validating LLM outputs, or building evaluation pipelines.

yonatangross/orchestkit · 55 tokens

bun-test-mocking

Use for mock functions in Bun tests, spyOn, mock.module, implementations, and test doubles.

secondsky/claude-skills · 25 tokens