A tool for evaluating and explaining Apollo EDU simulation scores from local race-data packages. Apollo is an autonomous-driving software platform, and the tool checks metrics such as reaching the end, time limits, collisions, road position, speed, acceleration, and turning forces.

It is for running offline score evaluations, interpreting metric results, and suggesting troubleshooting or tuning steps for Apollo simulator data.

It helps identify why a simulation passed or lost points and what scenario or driving settings may need investigation.

apollo-eval — Skill by ApolloAuto

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/apolloauto/apollo-claw/apollo-eval

Any agent

npx skills add ApolloAuto/apollo-claw --skill apollo-eval

Clone the repo

git clone --depth 1 https://github.com/ApolloAuto/apollo-claw

Made for: Claude Code, Codex.

Per session 293 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 4,643 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin unknown 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.

Model	Per session	Once invoked
Fable 5	$0.00293	$0.04643
Opus 5	$0.00147	$0.02322
Sonnet 5	$0.00059	$0.00929
Haiku 4.5	$0.00029	$0.00464

Measured 2d ago against content hash 3e1b7ca90ee9, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

apollo-eval 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 2d ago.

The scan reads SKILL.md. This mod also ships 28 executable files (scripts/extract_metrics.py, scripts/grading_system_py/__init__.py, scripts/grading_system_py/common/__init__.py, …), listed below but not scanned — reading those needs a real analyzer, not pattern matching.

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.

apollo-eval/SKILL.md · 358 lines

The source is not reproduced here

No licence file

Read it on GitHub

Files

What ships with it

60 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

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.

2d ago First seen · 358 lines · 293 tokens per session scan A 3e1b7ca90ee9

Subscribe to this mod's changes

apollo-eval is a skill published in the GitHub repository ApolloAuto/apollo-claw (5 stars, last pushed 3mo ago), with no licence file. It adds 293 tokens to every session and 4,643 once invoked, about $0.0015 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-08-31.

Analytics and metrics Debugging

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens

agent-host-chat-contributions

Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.

microsoft/vscode · 56 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens