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 skills add pangzhenying2025/hermes-automotive-skills --skill automotive-sotifgit clone --depth 1 https://github.com/pangzhenying2025/hermes-automotive-skillsWrote 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/pangzhenying2025/hermes-automotive-skills/automotive-sotif)<a href="https://agentmods.dev/skills/pangzhenying2025/hermes-automotive-skills/automotive-sotif"><img src="https://agentmods.dev/badge/skills/pangzhenying2025/hermes-automotive-skills/automotive-sotif/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.
<a href="https://agentmods.dev/skills/pangzhenying2025/hermes-automotive-skills/automotive-sotif"><img src="https://agentmods.dev/badge/skills/pangzhenying2025/hermes-automotive-skills/automotive-sotif.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00119 | $0.35059 |
| Opus 5 | $0.00060 | $0.17530 |
| Sonnet 5 | $0.00024 | $0.07012 |
| Haiku 4.5 | $0.00012 | $0.03506 |
Grade A, and why
automotive-sotif 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 9d 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.
How it starts
The opening of the file, as written. The whole thing — 4,417 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Automotive Sotif
15 skill files covering sotif domain for automotive software engineering.
Applicable Standards
- ASAM OpenDRIVE 1.7
- ASAM OpenSCENARIO 2.0
- GDPR (Data Privacy)
- ISO 11064 Ergonomics
- ISO 19206 Road Vehicles Ultrasonic
- ISO 21448 SOTIF
- ISO 26262 Functional Safety
- ISO 26262-3 (Hazard Analysis)
- ISO 26262-3 (Risk Assessment)
- ISO 26262-3 (Safety Goals)
- ISO 26262-4
- ISO 26262-4 (System Design)
- ISO 26262-4 (System Validation)
- ISO 26262-6 (Software Development)
- ISO 26262-6 (Software Validation)
- ISO 26262-8 (Supporting Processes)
- ISO 34502 Road Vehicle Test Scenarios
- ISO 34502 Road Vehicles Test Scenarios
- ISO 34502 Test Scenarios
- ISO/PAS 21448:2019
- ISO/TR 4804 Safety of AI
- ISO/TR 4804 Safety of AI in Road Vehicles
- NHTSA Driver Distraction Guidelines
- SAE J3016
- SAE J3016 Automation Levels
- UL 4600 Autonomous Systems
- UL 4600 Autonomous Systems Safety
- UN ECE R157 (ALKS Software Update)
- UN ECE R157 (ALKS)
Use Cases
- ML model safety assurance for perception/planning
- False positive/negative analysis
- Out-of-distribution detection
- Adversarial robustness testing
- Domain adaptation validation
- Fleet data collection and analysis
- Disengagement pattern identification
- Near-miss event detection
- Continuous SOTIF improvement post-deployment
- Safety performance monitoring
- Reasonably foreseeable misuse identification
- Mode confusion analysis and mitigation
- Driver monitoring system requirements
- HMI design for SOTIF compliance
- Takeover request strategy development
- ODD nominal condition specification
- Requirements derivation for Area 1 operation
- Verification test plan for nominal scenarios
- Performance baseline establishment
- Type approval demonstration of intended functionality
Topics Covered
Functional Insufficiency
- sotif-algorithm-insufficiency
- sotif-sensor-insufficiency
Functional Safety
- sotif-overview
Human Factors
- sotif-human-factors
Ml Safety
- sotif-ml-safety-assurance
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.
- 9d ago First seen · 4,417 lines · 119 tokens per session scan A 4938ecb4c546
automotive-sotif is a skill published in the GitHub repository pangzhenying2025/hermes-automotive-skills (5 stars, last pushed 3mo ago), licensed MIT. It adds 119 tokens to every session and 35,059 once invoked, about $0.0006 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.
Other skills, from other repositories
software-test-creation
Write failing tests for a TDD slice based on acceptance criteria and codebase conventions. Use when the "red" phase of red-green-refactor requires tests that define expected behavior before implementation exists. Discovers codebase test conventions first, writes test files that compile or parse but fail because the…
automotive-expert
Expert-level automotive systems, connected vehicles, fleet management, telematics, ADAS, and automotive software. Use when the user mentions connected car, fleet, telematics, ADAS, or vehicle, or when the task involves Automotive Systems, Technologies, Standards and Protocols, or Fleet Management.
acceptance-driven-development
Use when creating or changing a software project, or when the user explicitly requests ADD, acceptance criteria, or verifiable done conditions.
mk:nyquist
Test-to-requirement coverage mapping. Reads plan acceptance criteria and test files, produces a coverage gap report showing which requirements have no tests. Use during Phase 2 (Test) or Phase 4 (Review) to verify test completeness. Named after the Nyquist sampling theorem — sufficient test coverage prevents aliased…
gauntlex:doctor
Full GAUNTLEX environment health check — model reachable, ChromaDB writable, AVF fixtures pass, no unexpected outbound network (air-gap verification). Use before first run or when debugging failures.
acceptance-criteria-given-when-then
Use this skill when writing test-first, behavior-driven acceptance criteria in Given/When/Then format for a Salesforce user story. Covers happy path, edge cases, negative paths, permission boundaries, and data-state preconditions so the AC block can drive UAT scripts and Apex test design downstream. Trigger keywords…