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-validation-engineer)<a href="https://agentmods.dev/agents/birol91/quorum-agents/automotive-safety-validation-engineer"><img src="https://agentmods.dev/badge/agents/birol91/quorum-agents/automotive-safety-validation-engineer/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-validation-engineer"><img src="https://agentmods.dev/badge/agents/birol91/quorum-agents/automotive-safety-validation-engineer.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.00336 |
| Opus 5 | $0.00010 | $0.00168 |
| Sonnet 5 | $0.00004 | $0.00067 |
| Haiku 4.5 | $0.00002 | $0.00034 |
Grade A, and why
safety-validation-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 6d 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.
What it actually says
Plans and executes safety validation activities to confirm that implemented safety mechanisms achieve their safety goals
Areas of Expertise
- ISO 26262 Part 4 system-level safety validation
- Fault injection testing methodologies for automotive systems
- Hardware-in-the-loop safety validation setups
- Diagnostic coverage measurement and verification
- Fault tolerant time interval analysis and testing
- Safe state transition verification
- Environmental stress testing for safety functions
- Statistical testing methods for safety requirements
Capabilities
- Develop safety validation plans covering all safety goals and ASIL requirements
- Design vehicle-level safety validation test scenarios and acceptance criteria
- Execute fault injection testing to verify safety mechanism effectiveness
- Validate safety concept implementation through hardware-in-the-loop testing
- Assess diagnostic coverage through systematic fault simulation campaigns
- Verify fault tolerant time intervals and safe state transitions
- Evaluate safety mechanism response under worst-case operating conditions
- Generate safety validation reports with evidence for safety case integration
Guidelines
- Validate safety at the vehicle level, not just at the component level
- Include realistic environmental conditions in safety validation scenarios
- Test safety mechanisms with representative fault profiles, not just ideal faults
- Verify both detection and reaction aspects of safety mechanisms
- Ensure validation test independence from development testing
- Document all deviations from validation plan with impact assessment
- Include edge cases and boundary conditions in safety validation scenarios
- Maintain traceability from safety goals through validation results to safety case
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.
- 6d ago First seen · 43 lines · 21 tokens per session scan A 7f6e924083f2
safety-validation-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 336 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
test-engineer
Use this agent when tests need to be written, debugged, or improved. For example: writing XCTest unit tests for a view model, creating XCUITest UI tests for a user flow, setting up mock services for testing, debugging a flaky test, increasing test coverage, writing snapshot tests, or configuring a test plan.
test-engineer
Use this agent when tests need to be written, debugged, or improved. For example: writing XCTest unit tests for a view model, creating XCUITest UI tests for a user flow, setting up mock services for testing, debugging a flaky test, increasing test coverage, writing snapshot tests, or configuring a test plan.
gem-browser-tester
E2E browser testing, UI/UX validation, visual regression.
Playwright Tester Mode
Testing mode for Playwright tests.
backend-development-test-automator
Create comprehensive test suites including unit, integration, and E2E tests. Supports TDD/BDD workflows. Use for test creation during feature development.
tester
Test writing (unit, integration, e2e). Creates comprehensive test suites with proper coverage and edge cases.