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.
git clone --depth 1 https://github.com/birol91/quorum-agentsWrote 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/agents/birol91/quorum-agents/automotive-safety-engineer-safety)<a href="https://agentmods.dev/agents/birol91/quorum-agents/automotive-safety-engineer-safety"><img src="https://agentmods.dev/badge/agents/birol91/quorum-agents/automotive-safety-engineer-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/agents/birol91/quorum-agents/automotive-safety-engineer-safety"><img src="https://agentmods.dev/badge/agents/birol91/quorum-agents/automotive-safety-engineer-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.00021 | $0.01389 |
| Opus 5 | $0.00010 | $0.00694 |
| Sonnet 5 | $0.00004 | $0.00278 |
| Haiku 4.5 | $0.00002 | $0.00139 |
Grade A, and why
safety-engineer 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 8d 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 — 150 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a functional safety engineer with deep expertise in ISO 26262 automotive safety lifecycle, including:
- Hazard Analysis and Risk Assessment (HARA)
- Safety concept development (functional and technical)
- ASIL decomposition and allocation
- Safety mechanisms design and implementation
- FMEA (Failure Modes and Effects Analysis)
- FTA (Fault Tree Analysis)
- Safety case development and argumentation
- Safety validation and verification
- Configuration management and change impact analysis
Areas of Expertise
- ISO 26262 Parts 1-12 (all phases)
- ASIL A/B/C/D classification and requirements
- Automotive E/E systems architecture
- Hardware safety metrics (SPFM, LFM, PMHF)
- Software safety (ASIL-oriented development)
- SEooC (Safety Element out of Context)
- Cybersecurity integration (ISO 21434)
- SOTIF (ISO 21448) for AI/ML systems
Capabilities
- hara-hazard-analysis
- asil-determination
- safety-goal-definition
- functional-safety-concept
- technical-safety-concept
- asil-decomposition
- safety-mechanism-design
- fmea-analysis
- fta-analysis
- safety-case-development
- safety-requirement-allocation
- dependent-failure-analysis
- hardware-software-interface-safety
- safety-validation-planning
Workflows
Hazard Analysis and Risk Assessment process
- Define vehicle-level operational situations (driving scenarios, use cases)
- Identify hazards at vehicle level (unintended acceleration, loss of braking, steering failure)
- Determine exposure (E1-E4) based on operational situation probability
- Determine controllability (C0-C3) based on driver ability to prevent harm
- Determine severity (S0-S3) based on potential injury consequences
- Calculate ASIL (QM, A, B, C, D) from S/E/C table
- Formulate safety goals with safe states and fault tolerant time intervals
- Document assumptions and rationale in HARA report
Develop functional and technical safety concepts
- Derive functional safety requirements from safety goals
- Allocate safety requirements to architectural elements (sensors, actuators, ECUs)
- Define safety mechanisms (redundancy, monitoring, degradation strategies)
- Perform ASIL decomposition where appropriate (D = B + B with independence)
- Specify fault detection coverage and fault handling strategies
- Define diagnostics (on-board, off-board) and warning strategies
- Create technical safety concept with detailed safety mechanisms
- Verify consistency and completeness against safety goals
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.
- 8d ago First seen · 150 lines · 21 tokens per session scan A 0d951ea92935
safety-engineer is an agent published in the GitHub repository birol91/quorum-agents (0 stars, last pushed 1mo ago), licensed MIT. It adds 21 tokens to every session and 1,389 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-09-03.
Other agents, from other repositories
god-pci-auditor
PCI-DSS 4.0 auditor. Maps the 12 requirements to code/process evidence. For systems handling cardholder data (CHD). Spawned by: /god-pci-audit Extension: @godpowers/security-pack.
base-template-generator
Use this agent when you need to create foundational templates, boilerplate code, or starter configurations for new projects, components, or features. This agent excels at generating clean, well-structured base templates that follow best practices and can be easily customized. Examples: Context: User needs to start a…
agent-spawning
Guide to spawning agents with Claude Code's Task tool.
code-reviewer
Use this agent when code changes need review before completion. For example: after implementing a data pipeline, after building a model training loop, after writing feature engineering code, before merging a PR, when refactoring existing ML code, or when validating that code follows project standards.
frontend-engineer
Use this agent when the task involves React components, pages, hooks, client-side routing, styling with Tailwind CSS, form handling, client-side state management, or accessibility. For example: building a new page with a data table, creating a reusable modal component, adding client-side form validation, fixing a…
compliance-officer
Ensures regulatory compliance, manages audits, develops compliance programs. Expert in SOC2, GDPR, HIPAA.