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.
npx agentmods add commands/dartsim/dart/dart-prgit 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/commands/dartsim/dart/dart-pr)<a href="https://agentmods.dev/commands/dartsim/dart/dart-pr"><img src="https://agentmods.dev/badge/commands/dartsim/dart/dart-pr.svg" alt="Measured on agentmods" height="20"></a>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 | $0.00015 | $0.01231 |
| Opus 5 | $0.00008 | $0.00616 |
| Sonnet 5 | $0.00003 | $0.00246 |
| Haiku 4.5 | $0.00002 | $0.00123 |
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 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.
How it starts
The opening of the file, as written. The whole thing — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Prepare or open a DART pull request after explicit maintainer/user approval: $ARGUMENTS
Required Reading
@AGENTS.md @docs/onboarding/contributing.md @docs/onboarding/ai-reviews.md @docs/onboarding/changelog.md @.github/PULL_REQUEST_TEMPLATE.md
Recent PR Patterns
When the expected PR style is unclear, inspect recently merged PRs before drafting the title or body:
gh pr list --repo dartsim/dart --state merged --base main --limit 10 \
--json number,title,body,mergedAt
Use these practices:
- Keep titles plain, scoped, and outcome-focused. Do not add agent prefixes.
- Fill the PR template in DART's default order: Summary, Motivation / Problem, Changes / Key Changes, optional Before / After, Testing, Breaking Changes, and Related Issues / PRs. Keep Summary first because reviewers need the skimmable outcome before the rationale. If the motivation is necessary to understand the outcome, make the first Summary sentence problem-oriented, then keep the fuller why in Motivation / Problem rather than moving it above Summary.
- Write Summary and Motivation for a user or downstream maintainer unfamiliar with the implementation: lead with what changes for them, what stays compatible, how they opt in or migrate, and why the evidence matters. Keep implementation mechanics in Changes unless they explain a user-visible outcome or risk.
- When the change has user-facing API, workflow, behavior, or performance
impact, add a concise
## Before / Aftersection before Testing covering only relevant dimensions (public API, commands/workflows, behavior, migration, performance baseline). Phrase each row as a user-visible before/after, then name the mechanism as supporting context. For performance claims, name the baseline explicitly (CPU path, parent commit,main, or prior implementation) plus workload, metric, and limitations. - In Testing, list exact commands, targets, or test names that ran. For CI, performance, or infrastructure work, include evidence such as CI observations, timing, reruns, benchmark output, or why a skipped check is expected.
- For 3D structure or behavior changes (model/scene, dynamics,
collision/contact, simulation, rendering, GUI, visual examples), use
dart-verify-sim: report the text correctness oracle and assessed, claim-relevant visual/debug evidence (an image alone is not proof), captured before and after with the same camera, dimensions, and renderer, and include the commands. Publish transient evidence withpixi run evidence-publish(GitHub-hosted placeholders, or approved release assets) as described indocs/onboarding/agent-sim-verification.md; never commit transient evidence. - Mark non-applicable checklist items as "N/A" with a short reason, and mention related PRs, issues, backports, and follow-ups explicitly, including "None".
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.
- yesterday Changed · -17 lines c97ca9766ad8
- 3d ago First seen · 133 lines · 15 tokens per session scan A 227a4bb30dfc
dart-pr is a command published in the GitHub repository dartsim/dart (1,201 stars, last pushed today), licensed BSD-2-Clause. It adds 15 tokens to every session and 1,231 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 commands, from other repositories
commit-message
Suggest a clear and simple commit message for the current changes.
commit-push-pr
Commit, push, and open a PR.
cr
When user uses /cr slash command, review uncommitted code changes with reusable language-aware rules, preferring project-local review commands or rules when they exist.
commit
智能创建 git 提交，分析代码变更并生成符合项目规范的提交信息.
pr-review
Review the current branch changes and suggest PR content.
changelog
Summarize staged git changes into a concise changelog/commit message.