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-hardware-safetygit 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-hardware-safety)<a href="https://agentmods.dev/skills/pangzhenying2025/hermes-automotive-skills/automotive-hardware-safety"><img src="https://agentmods.dev/badge/skills/pangzhenying2025/hermes-automotive-skills/automotive-hardware-safety/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-hardware-safety"><img src="https://agentmods.dev/badge/skills/pangzhenying2025/hermes-automotive-skills/automotive-hardware-safety.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.00032 | $0.02993 |
| Opus 5 | $0.00016 | $0.01496 |
| Sonnet 5 | $0.00006 | $0.00599 |
| Haiku 4.5 | $0.00003 | $0.00299 |
Grade A, and why
automotive-hardware-safety 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 — 393 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Automotive Hardware Safety
4 skill files covering hardware-safety domain for automotive software engineering.
Instructions
Diagnostic Coverage Analysis
You are an expert in diagnostic coverage analysis per ISO 26262.
What is Diagnostic Coverage (DC): DC is the ratio of detected faults to total faults for a given failure mode.
Formula: DC = λ_detected / (λ_detected + λ_undetected)
Where:
- λ_detected: Failure rate detected by safety mechanism
- λ_undetected: Residual failure rate (not detected)
Diagnostic Coverage Levels (ISO 26262-5 Table 6):
- DC = 0%: None (no diagnostic)
- DC < 60%: Low
- 60% ≤ DC < 90%: Medium
- 90% ≤ DC < 99%: High
- DC ≥ 99%: Very High
Sources of Diagnostic Coverage:
1. Hardware Diagnostics:
- Plausibility checks (range, gradient, correlation)
- Redundancy and voting (dual sensors, triple modular redundancy)
- Self-tests (BIST, RAM/ROM tests)
- Watchdog timers
- Memory protection (ECC, parity, CRC)
- Voltage/temperature monitoring
2. Software Diagnostics:
- Control flow monitoring
- Data integrity checks (checksums, CRCs)
- Alive counters
- Sequence monitoring
- Logical execution time monitoring
Diagnostic Coverage by Mechanism:
| Safety Mechanism | Typical DC | ISO 26262 Reference |
|---|---|---|
| Plausibility check (range) | 60-70% | Part 5, Annex D |
| Dual sensor with voting | 90-95% | Part 5, Annex D |
| Triple modular redundancy | 99%+ | Part 5, Annex D |
| Watchdog timer | 90-95% | Part 6, Annex B |
| ECC memory | 95-99% | Part 5, Annex D |
| CRC on communication | 99%+ | Part 6, Annex B |
Calculating Overall DC:
For multiple diagnostics on same element: DC_total = 1 - Π(1 - DC_i) for independent diagnostics
Example:
- Plausibility check: DC1 = 70%
- Redundant sensor: DC2 = 90%
- DC_total = 1 - (1 - 0.7)(1 - 0.9) = 1 - (0.3)(0.1) = 1 - 0.03 = 97%
Verification of DC:
DC must be verified, not just claimed. Methods:
- Fault injection testing (software/hardware)
- Formal verification
- Analysis (for well-established mechanisms)
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 · 393 lines · 32 tokens per session scan A 1056e29e39e1
automotive-hardware-safety is a skill published in the GitHub repository pangzhenying2025/hermes-automotive-skills (5 stars, last pushed 3mo ago), licensed MIT. It adds 32 tokens to every session and 2,993 once invoked, about $0.0002 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-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.
run-pre-purchase-inspection
Use when evaluating a used vehicle before purchase to identify hidden defects, safety issues, and negotiate from an informed position.
design-ev-charging-setup
Use when planning or installing home EV charging equipment to select the right charger level, electrical requirements, and installation approach.
diagnose-battery-charging-problem
Use when a vehicle has starting problems, battery warning lights, or electrical symptoms — systematically testing battery condition, alternator output, and charging circuit integrity to identify the root cause before replacing components.
run-fluid-inspection-checklist
Use when performing a routine vehicle fluid inspection — checking engine oil, coolant, brake fluid, power steering fluid, transmission fluid, and windshield washer fluid levels and condition to catch problems before they become failures.