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-securitygit 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-security)<a href="https://agentmods.dev/skills/pangzhenying2025/hermes-automotive-skills/automotive-security"><img src="https://agentmods.dev/badge/skills/pangzhenying2025/hermes-automotive-skills/automotive-security/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-security"><img src="https://agentmods.dev/badge/skills/pangzhenying2025/hermes-automotive-skills/automotive-security.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.00052 | $0.18823 |
| Opus 5 | $0.00026 | $0.09412 |
| Sonnet 5 | $0.00010 | $0.03765 |
| Haiku 4.5 | $0.00005 | $0.01882 |
Grade A, and why
automotive-security 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.
This is a copy
91% identical to automotive-access-control — 756 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 4,244 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Automotive Security
198 skill files covering security domain for automotive software engineering.
Applicable Standards
- ASPICE Level 3
- AUTOSAR 4.4
- ISO 21434
- ISO 26262
Use Cases
- SECURITY system development
- Authentication optimization
- Production ECU implementation
- Cybersecurity optimization
- Encryption optimization
- Intrusion Detection optimization
- Key Management optimization
- Penetration Testing optimization
- Secure Boot optimization
- Secure Communication optimization
- Secure Ota optimization
- Threat Modeling optimization
- Vulnerability Assessment optimization
Topics Covered
Authentication
- authentication-001
- authentication-002
- authentication-003
- authentication-004
- authentication-005
- authentication-006
- authentication-007
- authentication-008
- authentication-009
- authentication-010
- authentication-011
- authentication-012
- authentication-013
- authentication-014
- authentication-015
- authentication-016
- authentication-017
- authentication-018
Cybersecurity
- cybersecurity-001
- cybersecurity-002
- cybersecurity-003
- cybersecurity-004
- cybersecurity-005
- cybersecurity-006
- cybersecurity-007
- cybersecurity-008
- cybersecurity-009
- cybersecurity-010
- cybersecurity-011
- cybersecurity-012
- cybersecurity-013
- cybersecurity-014
- cybersecurity-015
- cybersecurity-016
- cybersecurity-017
- cybersecurity-018
Encryption
- encryption-001
- encryption-002
- encryption-003
- encryption-004
- encryption-005
- encryption-006
- encryption-007
- encryption-008
- encryption-009
- encryption-010
- encryption-011
- encryption-012
- encryption-013
- encryption-014
- encryption-015
- encryption-016
- encryption-017
- encryption-018
Intrusion Detection
- intrusion-detection-001
- intrusion-detection-002
- intrusion-detection-003
- intrusion-detection-004
- intrusion-detection-005
- intrusion-detection-006
- intrusion-detection-007
- intrusion-detection-008
- intrusion-detection-009
- intrusion-detection-010
- intrusion-detection-011
- intrusion-detection-012
- intrusion-detection-013
- intrusion-detection-014
- intrusion-detection-015
- intrusion-detection-016
- intrusion-detection-017
- intrusion-detection-018
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,244 lines · 52 tokens per session scan A 55352202701d
automotive-security is a skill published in the GitHub repository pangzhenying2025/hermes-automotive-skills (5 stars, last pushed 3mo ago), licensed MIT. It adds 52 tokens to every session and 18,823 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to automotive-access-control, differing in 756 lines, and is treated as a copy.
Other skills, from other repositories
implementing-envelope-encryption-with-aws-kms
Envelope encryption is a strategy where data is encrypted with a data encryption key (DEK), and the DEK itself is encrypted with a master key (KEK) managed by AWS KMS. This approach allows encrypting.
api-security-testing
Security-test a REST, GraphQL, or gRPC API with Strix — autonomous agents that enumerate endpoints from an OpenAPI/GraphQL schema (or by crawling), then actually exploit the API-specific vulnerability classes in the OWASP API Security Top 10 (2023) — broken object-level authorization (BOLA/IDOR), broken object…
fix-security-vulnerabilities-with-strix
Fix security vulnerabilities found by a Strix pentest (open-source CLI or app.strix.ai cloud) — triage by severity, patch the root cause rather than the symptom, and re-run Strix to prove each fix actually closes the exploit. Handles injection, XSS, SSRF, broken access control, IDOR, and other validated findings. Use…
owasp-top-10-testing
Test an application against the OWASP Top 10 with Strix — autonomous AI agents that attempt real exploits for each category of the current OWASP Top 10:2025 (broken access control including SSRF, security misconfiguration, software supply chain failures, cryptographic failures, injection, insecure design…
find-security-vulnerabilities-in-code
Find security vulnerabilities in a codebase or repository with Strix — a white-box AI security review that reads your source, reasons about the actual data flow and authorization model, then exploits what it finds in a live sandbox so every reported issue has a working proof-of-concept instead of a noisy…
web-app-penetration-testing
Pentest a web app or website end to end — black-box testing of a live URL, staging environment, or local dev server that finds and exploits real vulnerabilities (auth bypass, broken access control, IDOR, injection, XSS, SSRF, business logic) and proves each one with a working proof-of-concept instead of a signature…