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-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-safety-analysis)<a href="https://agentmods.dev/skills/pangzhenying2025/hermes-automotive-skills/automotive-safety-analysis"><img src="https://agentmods.dev/badge/skills/pangzhenying2025/hermes-automotive-skills/automotive-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-safety-analysis"><img src="https://agentmods.dev/badge/skills/pangzhenying2025/hermes-automotive-skills/automotive-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.00033 | $0.02167 |
| Opus 5 | $0.00016 | $0.01084 |
| Sonnet 5 | $0.00007 | $0.00433 |
| Haiku 4.5 | $0.00003 | $0.00217 |
Grade A, and why
automotive-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 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 — 279 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Automotive Safety Analysis
4 skill files covering safety-analysis domain for automotive software engineering.
Instructions
DFA - Dependent Failure Analysis
You are an expert in DFA (Dependent Failure Analysis) for automotive safety.
What is DFA: DFA identifies and analyzes dependent failures (common cause failures) that can affect multiple elements simultaneously, defeating redundancy and safety mechanisms.
When Required:
- ISO 26262-9:7 mandates DFA for systems with redundancy
- ASIL decomposition requires DFA to verify independence
- Safety mechanisms with multiple channels (dual-core lockstep, redundant sensors)
Types of Dependent Failures:
1. Common Cause Failures (CCF)
- Single root cause affects multiple elements
- Example: Overvoltage damages both primary and backup ECU
2. Cascading Failures
- Failure of one element triggers failure of another
- Example: Sensor failure causes incorrect actuator command
3. Common Mode Failures (CMF)
- Same failure mode in redundant elements
- Example: Both sensors drift due to aging
DFA Process:
Step 1: Identify Redundant/Independent Elements
- Dual-core lockstep CPUs
- Redundant sensors (2x wheel speed sensors)
- Backup power supplies
- Independent software partitions
Step 2: Identify Coupling Factors
- Physical coupling (shared power, thermal)
- Functional coupling (shared algorithms, data)
- Environmental coupling (EMI, temperature, vibration)
- Systematic coupling (common design flaw, software bug)
Step 3: Evaluate Coupling
- Weak coupling: Acceptable (< 1% probability)
- Strong coupling: Unacceptable (requires mitigation)
Step 4: Mitigation
- Physical separation (spatial diversity)
- Temporal separation (different execution times)
- Design diversity (different implementations)
- Shielding/isolation (EMC, thermal barriers)
DFA Checklist (ISO 26262-9 Table 3):
- External factors (EMI, temperature, vibration, humidity, dust)
- Internal factors (power supply, clock, memory)
- Software factors (common libraries, OS, compiler)
- Manufacturing (common production line, supplier)
- Maintenance (same service procedure, tools)
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 · 279 lines · 33 tokens per session scan A f27a5e5e417d
automotive-safety-analysis is a skill published in the GitHub repository pangzhenying2025/hermes-automotive-skills (5 stars, last pushed 3mo ago), licensed MIT. It adds 33 tokens to every session and 2,167 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-09-03.
Other skills, from other repositories
research-engineer
An uncompromising Academic Research Engineer. Operates with absolute scientific rigor, objective criticism, and zero flair. Focuses on theoretical correctness, formal verification, and optimal implementation across any required technology.
train-pose
Train/evaluate WiFi pose models honestly — camera-supervised (MediaPipe + CSI) and camera-free (WiFlow), always checked against the mean-pose baseline before any PCK is quoted.
experiment-audit
A review step that checks whether an experiment's reported results are supported by real data and a sufficiently broad test.
i4h-catheter-navigation-e2e
End-to-end smoke for catheter navigation covering setup, digital twin, DRR, and unit tests. Use when asked to run the full catheter workflow smoke or demo the v0.7 pipeline.
i4h-catheter-navigation-render-drr
Render a single DRR fluoroscopy frame from a CT cache or synthetic phantom. Use when asked to render DRR, generate a fluoro image, or smoke-test the Slang renderer.
i4h-catheter-navigation-smoke
Run CPU-only fluorosim smoke tests (imports, preprocessing, CLI parsers). Use when asked to smoke-test catheter navigation in CI or without a GPU.