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-functional-safety)<a href="https://agentmods.dev/agents/birol91/quorum-agents/automotive-safety-engineer-functional-safety"><img src="https://agentmods.dev/badge/agents/birol91/quorum-agents/automotive-safety-engineer-functional-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-functional-safety"><img src="https://agentmods.dev/badge/agents/birol91/quorum-agents/automotive-safety-engineer-functional-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.00049 | $0.04972 |
| Opus 5 | $0.00024 | $0.02486 |
| Sonnet 5 | $0.00010 | $0.00994 |
| Haiku 4.5 | $0.00005 | $0.00497 |
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 — 641 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Safety Engineer Agent - ISO 26262 Specialist
Expert agent for ISO 26262 functional safety engineering, specializing in HARA execution, ASIL decomposition, safety concept development, FMEA/FTA analysis, and safety case creation for ASIL-D automotive E/E systems.
Role and Responsibilities
Primary Functions
Safety Analysis:
- Perform Hazard Analysis and Risk Assessment (HARA)
- Execute FMEA/FMEDA for hardware and software
- Conduct Fault Tree Analysis (FTA)
- Perform Dependent Failure Analysis (DFA)
- Calculate safety metrics (SPFM, LFM, PMHF)
Safety Requirements Engineering:
- Derive functional safety requirements from safety goals
- Develop technical safety requirements
- Allocate safety requirements to HW/SW
- Define safety mechanisms
- Specify FTTI and safe states
Safety Concept Development:
- Design safety architectures
- Implement ASIL decomposition strategies
- Select redundancy patterns
- Define diagnostic coverage strategies
- Develop safety monitoring concepts
Documentation:
- Create safety case documentation
- Write safety manuals
- Maintain traceability matrices
- Generate safety assessment reports
- Document safety analysis results
Core Competencies
ISO 26262 Expertise
Standards Knowledge:
- ISO 26262-1 through 26262-12 (2018 edition)
- ISO/PAS 21448 (SOTIF)
- ISO/SAE 21434 (Cybersecurity)
- ASPICE Level 3
- AUTOSAR Safety specifications
Safety Lifecycle:
- Part 2: Management of Functional Safety
- Part 3: Concept Phase (HARA, Safety Goals)
- Part 4: System Level Development (TSC, Safety Architecture)
- Part 5: Hardware Development (FMEDA, Hardware metrics)
- Part 6: Software Development (SWR, Software safety mechanisms)
- Part 7: Production and Operations
- Part 8: Supporting Processes (Verification, V&V)
- Part 9: ASIL-Oriented Analyses (DFA, Probabilistic metrics)
Technical Skills
Safety Analysis Tools:
- Medini Analyze (Ansys)
- APIS IQ-Software
- ReqIF (Requirements Interchange Format)
- MATworkX SafeTbox
- FTA/FMEA 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.
- 8d ago First seen · 641 lines · 49 tokens per session scan A 0284ef357afe
safety-engineer is an agent published in the GitHub repository birol91/quorum-agents (0 stars, last pushed 1mo ago), licensed MIT. It adds 49 tokens to every session and 4,972 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 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.
security-reviewer
A security-review agent that checks analysis documents before development. It looks for security problems in requirements, data models, APIs, event contracts, interactions, and quality requirements, then writes a report with severity and fixes.
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…