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-access-controlgit 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-access-control)<a href="https://agentmods.dev/skills/pangzhenying2025/hermes-automotive-skills/automotive-access-control"><img src="https://agentmods.dev/badge/skills/pangzhenying2025/hermes-automotive-skills/automotive-access-control/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-access-control"><img src="https://agentmods.dev/badge/skills/pangzhenying2025/hermes-automotive-skills/automotive-access-control.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.00055 | $0.04067 |
| Opus 5 | $0.00028 | $0.02034 |
| Sonnet 5 | $0.00011 | $0.00813 |
| Haiku 4.5 | $0.00006 | $0.00407 |
Grade A, and why
automotive-access-control 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.
Copies of this mod
8 near-identical copies found in the catalogue:
- automotive-security — 91% identical, 756 lines differ
- automotive-network — 91% identical, 959 lines differ
- automotive-exhaust — 89% identical, 268 lines differ
- automotive-comfort — 88% identical, 268 lines differ
- automotive-embedded — 88% identical, 1,004 lines differ
- automotive-body — 86% identical, 520 lines differ
- automotive-navigation — 86% identical, 268 lines differ
- automotive-lighting — 86% identical, 428 lines differ
How it starts
The opening of the file, as written. The whole thing — 898 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Automotive Access Control
40 skill files covering access-control domain for automotive software engineering.
Applicable Standards
- ASPICE Level 3
- AUTOSAR 4.4
- ISO 21434
- ISO 26262
Use Cases
- ACCESS-CONTROL system development
- Biometric optimization
- Production ECU implementation
- Nfc Key optimization
- Phone As Key optimization
- Smart Key optimization
Topics Covered
Biometric
- biometric-001
- biometric-002
- biometric-003
- biometric-004
- biometric-005
- biometric-006
- biometric-007
- biometric-008
- biometric-009
- biometric-010
Nfc Key
- nfc-key-001
- nfc-key-002
- nfc-key-003
- nfc-key-004
- nfc-key-005
- nfc-key-006
- nfc-key-007
- nfc-key-008
- nfc-key-009
- nfc-key-010
Phone As Key
- phone-as-key-001
- phone-as-key-002
- phone-as-key-003
- phone-as-key-004
- phone-as-key-005
- phone-as-key-006
- phone-as-key-007
- phone-as-key-008
- phone-as-key-009
- phone-as-key-010
Smart Key
- smart-key-001
- smart-key-002
- smart-key-003
- smart-key-004
- smart-key-005
- smart-key-006
- smart-key-007
- smart-key-008
- smart-key-009
- smart-key-010
Constraints
- AUTOSAR architecture adherence
- ISO 26262 functional safety compliance
- Real-time performance requirements
- Resource constraints (CPU/Memory)
Required Tools
- AUTOSAR toolchain
- MATLAB/Simulink
- Static analyzer (Polyspace/Klocwork)
- Vector CANoe/CANalyzer
Instructions
biometric-001
Core Competencies
Expert in biometric for automotive access-control systems.
Approach
- Analyze requirements against automotive standards
- Design solution following AUTOSAR patterns
- Implement with safety and security considerations
- Validate per ISO 26262 requirements
Deliverables
- Technical specification
- Implementation (C/C++/Model)
- Test cases and results
- Safety documentation
biometric-002
Core Competencies
Expert in biometric for automotive access-control systems.
Approach
- Analyze requirements against automotive standards
- Design solution following AUTOSAR patterns
- Implement with safety and security considerations
- Validate per ISO 26262 requirements
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 · 898 lines · 55 tokens per session scan A 2037a260d4da
automotive-access-control is a skill published in the GitHub repository pangzhenying2025/hermes-automotive-skills (5 stars, last pushed 3mo ago), licensed MIT. It adds 55 tokens to every session and 4,067 once invoked, about $0.0003 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
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.
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…
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 /…