automotive-scenario-driven-testing

automotive-scenario-driven-testing is a skill for Claude Code, Codex from pangzhenying2025/hermes-automotive-skills. It costs 23 tokens per session (2,193 once invoked), scanned A, original, MIT.

A testing method for advanced driver-assistance and automated-driving systems that evaluates defined driving situations instead of relying only on total kilometres driven. It combines real-world driving data, simulation, test tracks, and road testing.

In plain words
What is it for?
Use it to extract driving scenarios, create variations, run simulation and vehicle tests, measure scenario coverage, and build safety evidence.
Why use it?
It helps teams test important situations systematically and collect evidence about safety. This gives clearer coverage than simply counting incidents over many kilometres.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit Use it to extract driving scenarios, create variations, run simulation and vehicle tests, measure scenario coverage, and build safety evidence.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/pangzhenying2025/hermes-automotive-skills/automotive-scenario-driven-testing
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 pangzhenying2025/hermes-automotive-skills --skill automotive-scenario-driven-testing
Clone the repo
git clone --depth 1 https://github.com/pangzhenying2025/hermes-automotive-skills

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 automotive-scenario-driven-testing

README.md
[![agentmods](https://agentmods.dev/badge/skills/pangzhenying2025/hermes-automotive-skills/automotive-scenario-driven-testing/github.svg)](https://agentmods.dev/skills/pangzhenying2025/hermes-automotive-skills/automotive-scenario-driven-testing)
Your own site
<a href="https://agentmods.dev/skills/pangzhenying2025/hermes-automotive-skills/automotive-scenario-driven-testing"><img src="https://agentmods.dev/badge/skills/pangzhenying2025/hermes-automotive-skills/automotive-scenario-driven-testing/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 automotive-scenario-driven-testing

Your own site · 80×15
<a href="https://agentmods.dev/skills/pangzhenying2025/hermes-automotive-skills/automotive-scenario-driven-testing"><img src="https://agentmods.dev/badge/skills/pangzhenying2025/hermes-automotive-skills/automotive-scenario-driven-testing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 23 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,193 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.
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.00023 $0.02193
Opus 5 $0.00012 $0.01097
Sonnet 5 $0.00005 $0.00439
Haiku 4.5 $0.00002 $0.00219

Measured 8d ago against content hash 78d47c6b43e2, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

automotive-scenario-driven-testing 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.

skills/automotive-scenario-driven-testing/SKILL.md · 264 lines

How it starts

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

Automotive Scenario Driven Testing

Scenario Driven Testing

Scenario-Driven Testing & Evaluation — Methodology for ADAS/ADS V&V

Overview

Comprehensive methodology for scenario-driven testing and evaluation of ADAS/ADS systems. Integrates naturalistic driving data analysis, scenario extraction, simulation-track-road combined testing, and statistical evidence generation. This approach bridges the gap between traditional mileage-based testing and systematic scenario-based validation.

The Scenario-Driven V&V Paradigm

场景驱动测试评价范式
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Traditional Approach (传统方法):
  Drive millions of km → Count incidents → Statistically argue safety
  Problem: 10^8 km needed for L3, impractical

Scenario-Driven Approach (场景驱动方法):
  1. Extract scenarios from NDD/accidents/standards
  2. Parameterize and generate variations
  3. Test systematically across parameter space
  4. Quantify risk per scenario type
  5. Aggregate to overall safety argument

  Advantage: 10^3 scenarios × 10^3 variations = comprehensive coverage
             with 10^4 - 10^5 km equivalent testing
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

Scenario Sources & Extraction

Source 1: Naturalistic Driving Data (NDD)

# NDD-based scenario extraction pipeline
class NaturalisticDrivingScenarioExtractor:
    """
    Extract test scenarios from naturalistic driving data.
    Based on DRIVEResearch methodology with 7.5M+ aerial trajectories.
    """

    def __init__(self, dataset_path: str):
        self.dataset = load_trajectory_dataset(dataset_path)

    def extract_critical_events(self,
                                 ttc_threshold: float = 3.0,
                                 thw_threshold: float = 1.5,
                                 decel_threshold: float = -4.0):
        """
        Extract safety-critical events from trajectory data.

        Criticality indicators:
        - TTC (Time-to-Collision) < threshold
        - THW (Time Headway) < threshold
        - Hard braking (deceleration < threshold)
        - Near-miss events
        """
        critical_events = []
        for trajectory in self.dataset:
            for timestep in trajectory:
                if (timestep.ttc < ttc_threshold or
                    timestep.thw < thw_threshold or
                    timestep.acceleration < decel_threshold):
                    critical_events.append(
                        self.extract_scenario_context(trajectory, timestep)
                    )
        return critical_events

    def cluster_scenarios(self, events, method="spectral"):
        """
        Cluster similar events into scenario types.
        Methods: k-means, DBSCAN, spectral, GMM
        """
        features = self.extract_features(events)
        clusters = cluster_algorithm(features, method)
        return self.create_scenario_templates(clusters)

    def parameterize_scenario(self, template):
        """
        Create parameterized scenario from template.
        Output: OpenSCENARIO 2.0 compatible definition
        """
        return {
            "scenario_type": template.type,
            "parameters": {
                "ego_speed": Distribution(template.ego_speed_stats),
                "target_speed": Distribution(template.target_speed_stats),
                "relative_distance": Distribution(template.distance_stats),
                "lateral_offset": Distribution(template.offset_stats),
            },
            "criticality_distribution": template.criticality_dist,
            "exposure_frequency": template.occurrence_rate,
        }

Read the full file on GitHub · 264 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 First seen · 264 lines · 23 tokens per session scan A 78d47c6b43e2

Subscribe to this mod's changes

automotive-scenario-driven-testing is a skill published in the GitHub repository pangzhenying2025/hermes-automotive-skills (5 stars, last pushed 3mo ago), licensed MIT. It adds 23 tokens to every session and 2,193 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-03.

Related

Other skills, from other repositories

end-to-end-bioinformatics-pipeline-testing

Use when after cloning or installing a peak-calling or genomic analysis tool from a repository, before using it on production data.

HolobiomicsLab/asb-skill-collections · 35 tokens

iso26262

ISO 26262 functional-safety expert that operates in two modes: (1) HARA / ASIL determination — enumerate hazardous events from item malfunctions × driving situations, rate Severity (S0–S3), Exposure (E0–E4), Controllability (C0–C3), look up ASIL from ISO 26262-3:2018 Table 4, and produce a HARA report with Safety…

ptsilivis/autonomousguy · 197 tokens

automotive-syseng

When the user wants to analyze automotive requirements, check INCOSE/EARS compliance, review MISRA-C code, assess ADAS levels, or verify ISO 26262/AUTOSAR/SOTIF conformance. Also use when the user says 'check requirements', 'EARS check', 'INCOSE analysis', 'MISRA check', 'ASIL assessment', 'V-model check'…

duonghvu/automotive-syseng · 122 tokens

ftl:rhdp-lab-validator

This skill should be used when the user asks to "write solve and validate playbooks", "add E2E testing to my lab", "generate solve.yml", "generate validate.yml", "add solve and validate buttons", "set up runtime automation", "add ZT grading to my lab", "set up load testing for my lab", "add Demolition grading", or…

rhpds/rhdp-skills-marketplace · 94 tokens

test-warp-ui

Guides testing Warp UI features and changes using the computer use tool. Use this skill only when computer-use testing was requested (explicit request or accepted offer) and the computeruse tool is available to the agent. Covers launching Warp and verifying UI behavior.

warpdotdev/warp · 55 tokens

test-electron-app

Drive the real running PostHog Electron app (live tRPC, workspace-server, real data) over CDP with agent-browser. Connect to the running app on port 9222, test desktop changes against a local Django stack, snapshot the accessibility tree, inspect network requests, and screenshot only when explicitly asked. Use when…

PostHog/posthog-foss · 112 tokens