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-logginggit 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-logging)<a href="https://agentmods.dev/skills/pangzhenying2025/hermes-automotive-skills/automotive-logging"><img src="https://agentmods.dev/badge/skills/pangzhenying2025/hermes-automotive-skills/automotive-logging/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-logging"><img src="https://agentmods.dev/badge/skills/pangzhenying2025/hermes-automotive-skills/automotive-logging.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.00025 | $0.01320 |
| Opus 5 | $0.00013 | $0.00660 |
| Sonnet 5 | $0.00005 | $0.00264 |
| Haiku 4.5 | $0.00003 | $0.00132 |
Grade A, and why
automotive-logging 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 — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Automotive Logging
1 skill files covering logging domain for automotive software engineering.
Required Tools
- DLT Viewer (optional, for visualization)
- Python 3.8+
- dlt-daemon (optional, for network logging)
Instructions
dlt-logging
DLT (Diagnostic Log and Trace) Guide — AUTOSAR/COVESA
Overview
DLT is the standardized logging framework for automotive systems, defined by AUTOSAR and maintained by COVESA. It provides structured, high-performance logging with application/context-based filtering, binary message format for efficiency, and support for multi-ECU log aggregation.
Architecture
Application 1 Application 2 Application N
┌─────────────┐ ┌─────────────┐ ┌─────────────┐
│ DLT User │ │ DLT User │ │ DLT User │
│ Library │ │ Library │ │ Library │
└──────┬──────┘ └──────┬──────┘ └──────┬──────┘
│ │ │
└───────────────────┼───────────────────┘
│ UNIX Socket / Shared Memory
┌────────┴────────┐
│ DLT Daemon │
│ (dlt-daemon) │
├─────────────────┤
│ File Output │ → /var/log/dlt/*.dlt
│ Network Output │ → TCP port 3490
│ Serial Output │ → /dev/ttyS0
└─────────────────┘
│ TCP/IP
┌────────┴────────┐
│ DLT Viewer │ (Desktop analysis tool)
└─────────────────┘
Identification Model
DLT uses a hierarchical ID system for filtering:
- ECU ID (4 chars): Identifies the hardware unit (e.g., "ECU1", "GW01")
- Application ID (4 chars): Identifies the software application (e.g., "ADAS", "DIAG")
- Context ID (4 chars): Identifies the subsystem within an app (e.g., "CTRL", "SENS")
This enables precise filtering: show only ADAS.CTRL errors from ECU1.
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 · 148 lines · 25 tokens per session scan A d2157777c1ed
automotive-logging is a skill published in the GitHub repository pangzhenying2025/hermes-automotive-skills (5 stars, last pushed 3mo ago), licensed MIT. It adds 25 tokens to every session and 1,320 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.
embedded-debugging
Senior embedded debugging expert. Defaults to Classic AUTOSAR on ARM Cortex-M/R targets and operates in two modes: (1) Problem-report triage — take a field PR / bug ticket and produce symptom classification, affected-element mapping, ranked hypotheses, data-collection plan, and step-by-step investigation; (2) Targeted…
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.
diagnose-electrical-fault
Use when a vehicle has a blown fuse, inoperative accessory, warning light, or intermittent electrical failure — applying a systematic test sequence (visual, OBD-II codes, voltage/continuity testing) to isolate the fault to a specific component or circuit without replacing parts blindly.