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.
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.
curl -O https://raw.githubusercontent.com/dartsim/dart/main/.agents/skills/dart-fix-issue/SKILL.mdgit clone --depth 1 https://github.com/dartsim/dartWrote 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.
[](https://agentmods.dev/skills/dartsim/dart/dart-fix-issue)<a href="https://agentmods.dev/skills/dartsim/dart/dart-fix-issue"><img src="https://agentmods.dev/badge/skills/dartsim/dart/dart-fix-issue.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00022 | $0.00671 |
| Opus 5 | $0.00011 | $0.00336 |
| Sonnet 5 | $0.00004 | $0.00134 |
| Haiku 4.5 | $0.00002 | $0.00067 |
Grade A, and why
dart-fix-issue 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.
How it starts
The opening of the file, as written. The whole thing — 70 lines — stays where its author put it; the contents beside it link to each section on GitHub.
dart-fix-issue
Use this skill in Codex to run the DART dart-fix-issue 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-fix-issue <arguments> - Codex:
$dart-fix-issue <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
Fix GitHub issue: $ARGUMENTS
Required Reading
@AGENTS.md @docs/onboarding/contributing.md @docs/onboarding/changelog.md @docs/ai/verification.md
Workflow
If the fix depends on 3D structure or behavior, route through
dart-verify-sim: text oracle plus assessed visual evidence, or a recorded
exception.
gh issue view $1- Validate issue- Classify whether the issue is a bug fix that applies to the active DART 6
LTS branch. For applicable bug fixes, start from the highest maintained
origin/release-6.*branch; otherwise start fromorigin/main. - Fix with minimal changes + add regression test. For dual-PR bug fixes, fix
the active DART 6 LTS branch first, then cherry-pick or reapply to
main. - For an intermediate commit or PR, preserve and update the active task folder.
In the completing change, follow
docs/dev_tasks/README.md: complete feasible work, promote durable artifacts, and remove the folder before final validation and commit. Preserve its approval requirement for retiring unfinished work. pixi run lint, then the smallest relevant tests and the task-type gate set fromdocs/ai/verification.md- Before PR creation, invoke the
dart-changelogroutine to decide whetherCHANGELOG.mdneeds an entry, then fill.github/PULL_REQUEST_TEMPLATE.md. - After explicit maintainer/user approval,
git push -u origin HEAD && gh pr create --base <target-branch> --milestone "<milestone>"
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.
- today Changed · +3 lines 75b963096dd9
- 4d ago Changed · -3 lines 29866760a63f
- 6d ago First seen · 70 lines · 22 tokens per session scan A e4b54fa36b15
dart-fix-issue is a skill published in the GitHub repository dartsim/dart (1,202 stars, last pushed yesterday), licensed BSD-2-Clause. It adds 22 tokens to every session and 671 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.
Other skills, from other repositories
testing
Skill validation framework PLUS daily test-suite health and regression intelligence. Validates skill conformance (frontmatter, manifest coverage, resolver coverage). Runs the project test suite in tiered phases (unit / evals / integration / system health), classifies failures, and produces a regression-aware report.
verify
Verify that a change really works before you claim completion.
detect-static-dependencies
Scan C# source files for hard-to-test static dependencies — DateTime.Now/UtcNow, File., Directory., Environment., HttpClient, Console., Process., and other untestable statics. Produces a ranked report of static call sites by frequency. USE FOR: find untestable statics, scan for static dependencies, testability audit…
experiment-iterative-coder
Iterative code refinement through plan → code → evaluate → refine cycles. Runs lint checks (ruff), tests (pytest), and structured self-evaluation each cycle, then diagnoses failures and refines. Decomposes complex tasks into sequential phases, iterates up to 3 times per phase (10 total). Use when: the main agent…
testing-blocks
Use this when you have made AEM Edge Delivery Services code changes to blocks, scripts, or styles and need to validate them before opening a pull request. Covers unit testing for utilities and logic, browser testing with Playwright, linting, and guidance on what to test and how.
symbolic-execution-assistant
Performs symbolic execution to detect potential errors by exploring execution paths, solving path constraints, and generating test inputs. Use when you need to analyze code for bugs like null dereferences, division by zero, buffer overflows, or assertion violations. Also use to generate test inputs that exercise…