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-e2e-safety-analysisgit 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-e2e-safety-analysis)<a href="https://agentmods.dev/skills/pangzhenying2025/hermes-automotive-skills/automotive-e2e-safety-analysis"><img src="https://agentmods.dev/badge/skills/pangzhenying2025/hermes-automotive-skills/automotive-e2e-safety-analysis/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-e2e-safety-analysis"><img src="https://agentmods.dev/badge/skills/pangzhenying2025/hermes-automotive-skills/automotive-e2e-safety-analysis.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.00029 | $0.02339 |
| Opus 5 | $0.00015 | $0.01170 |
| Sonnet 5 | $0.00006 | $0.00468 |
| Haiku 4.5 | $0.00003 | $0.00234 |
Grade A, and why
automotive-e2e-safety-analysis 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 12d 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 — 262 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Automotive E2E Safety Analysis
E2E Safety Analysis
End-to-End Autonomous Driving Safety Analysis
Overview
Safety analysis framework for end-to-end (E2E) autonomous driving systems that use neural networks for the complete perception-to-control pipeline. Addresses the unique safety challenges of E2E architectures including interpretability, verification, functional safety compliance, and SOTIF analysis for learned driving policies.
E2E Architecture Safety Landscape
端到端自动驾驶安全分析框架
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Traditional Modular Stack:
Sensors → Perception → Prediction → Planning → Control
✓ Each module independently verifiable
✓ Clear failure mode attribution
✗ Information loss at interfaces
✗ Cumulative error propagation
End-to-End Architecture:
Sensors → [Neural Network] → Control
✓ No information loss (raw sensor to action)
✓ Potentially better performance (holistic optimization)
✗ Black-box: hard to verify/interpret
✗ No clear failure mode attribution
✗ ISO 26262 / SOTIF compliance challenges
Hybrid Architecture (现阶段主流):
Sensors → [E2E Backbone] → Structured Output → Safety Layer → Control
├── E2E handles perception + prediction + planning
├── Safety layer provides guardrails and override
├── Structured intermediate representations for interpretability
└── Fallback to rule-based system when confidence low
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Safety Challenges Unique to E2E
Challenge Matrix
e2e_safety_challenges = {
"interpretability": {
"problem": "Cannot explain why a specific driving decision was made",
"impact_on_safety": "Cannot perform systematic failure mode analysis",
"mitigation_approaches": [
"Attention map visualization",
"Intermediate representation extraction",
"Concept-based explanations",
"Counterfactual analysis",
"Structured output heads (BEV, occupancy, trajectory)",
],
},
"verification": {
"problem": "Traditional V&V methods insufficient for DNN",
"impact_on_safety": "Cannot guarantee behavior in unseen scenarios",
"mitigation_approaches": [
"Massive scenario-based testing",
"Formal verification of safety envelope",
"Runtime monitoring and intervention",
"Statistical safety arguments",
"Neuron coverage and mutation testing",
],
},
"functional_safety_compliance": {
"problem": "ISO 26262 assumes decomposable system architecture",
"impact_on_safety": "ASIL allocation and decomposition challenging",
"mitigation_approaches": [
"Safety wrapper / safety cage architecture",
"E2E as QM, safety layer as ASIL-rated",
"Redundant conventional perception for monitoring",
"ASIL decomposition at system level",
"1oo2D architecture (E2E + rule-based)",
],
},
"sotif_analysis": {
"problem": "Triggering conditions for DNN are fundamentally different",
"impact_on_safety": "Unknown-unsafe area potentially larger",
"mitigation_approaches": [
"Out-of-distribution detection",
"Uncertainty quantification (epistemic + aleatoric)",
"Domain adaptation and generalization testing",
"Adversarial robustness testing",
"Continuous learning with safety constraints",
],
},
"data_dependency": {
"problem": "Model behavior determined by training data distribution",
"impact_on_safety": "Bias, gaps, and distributional shift",
"mitigation_approaches": [
"Training data coverage analysis",
"Data augmentation for rare scenarios",
"Sim-to-real transfer validation",
"Geographic/cultural diversity in data",
"Data quality monitoring pipeline",
],
},
}
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.
- 12d ago First seen · 262 lines · 29 tokens per session scan A 9027f6274a4b
automotive-e2e-safety-analysis is a skill published in the GitHub repository pangzhenying2025/hermes-automotive-skills (5 stars, last pushed 3mo ago), licensed MIT. It adds 29 tokens to every session and 2,339 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-08-31.
Other skills, from other repositories
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…
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'…
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.
codebase-analysis
First-run skill that walks the entire repository, auto-detects Classic vs Adaptive AUTOSAR, and maps it accordingly. For Classic (default): identifies features and SWCs and documents referenced requirement IDs (SW-REQ-, REQ-, FSR-, SYS-REQ-), port interfaces (S/R, C/S, Mode Switch, Parameter), dependencies on other…
autosar-bsw
AUTOSAR BSW expert. Defaults to Classic AUTOSAR (BSW/MCAL/RTE, static config, C, AUTOSAR OS) and operates in six modes: (1) BSW configuration — Com, NvM, Dem, Dcm, Os, MemIf with dependency chain and EB Tresos / DaVinci container paths; (2) ARXML debugging — classify, locate, and fix consistency errors with a…
autosar-swc
AUTOSAR SWC expert. Defaults to Classic AUTOSAR (SWCs, RTE, ARXML, C) and operates in five modes: (1) Component design — decompose a feature into SWC types, define port interfaces, specify runnables and ExclusiveAreas, produce a plain-text composition diagram; (2) Interface definition — SenderReceiver / ClientServer /…