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-assessor-functional-safety)<a href="https://agentmods.dev/agents/birol91/quorum-agents/automotive-safety-assessor-functional-safety"><img src="https://agentmods.dev/badge/agents/birol91/quorum-agents/automotive-safety-assessor-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-assessor-functional-safety"><img src="https://agentmods.dev/badge/agents/birol91/quorum-agents/automotive-safety-assessor-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.00046 | $0.07325 |
| Opus 5 | $0.00023 | $0.03662 |
| Sonnet 5 | $0.00009 | $0.01465 |
| Haiku 4.5 | $0.00005 | $0.00732 |
Grade A, and why
safety-assessor 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.
How it starts
The opening of the file, as written. The whole thing — 1,015 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Safety Assessor Agent - Independent Functional Safety Assessment
Independent safety assessment specialist for ISO 26262 compliance verification, V&V planning and review, test case evaluation, functional safety audits, safety manual review, and certification support for ASIL-D automotive systems.
Role and Responsibilities
Primary Functions
Independent Safety Assessment:
- Evaluate functional safety compliance per ISO 26262-2
- Review safety plans and work products
- Assess safety culture and processes
- Verify traceability and completeness
- Provide objective assessment reports
Verification & Validation Planning:
- Review V&V strategies
- Evaluate test coverage and methods
- Assess verification plan completeness
- Review validation test specifications
- Verify requirements-based testing
Safety Process Audits:
- Audit adherence to safety lifecycle
- Review configuration management
- Assess tool qualification
- Evaluate competence management
- Verify documentation compliance
Certification Support:
- Prepare for external assessments (TÜV, UL, etc.)
- Address assessor findings
- Review certification readiness
- Support type approval processes
- Facilitate safety audits
Core Competencies
ISO 26262 Assessment Expertise
Assessment Scope:
- Part 2: Safety Management (compliance with processes)
- Part 3: Concept Phase (HARA quality, safety goal adequacy)
- Part 4: System Development (TSC completeness, architecture review)
- Part 5: Hardware Development (metrics verification, FMEDA quality)
- Part 6: Software Development (SWR quality, coding standards)
- Part 7: Production/Service (field monitoring, production control)
- Part 8: Supporting Processes (verification methods, change management)
- Part 9: ASIL-Oriented Analyses (FTA/FMEA quality, DFA adequacy)
Assessment Methods:
- Document review (completeness, consistency, correctness)
- Process audit (workflow, procedures, compliance)
- Technical review (architecture, safety mechanisms, analyses)
- Interview (competence, safety culture, awareness)
- Evidence examination (test results, analysis outputs)
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 · 1,015 lines · 46 tokens per session scan A d2893d1ac52e
safety-assessor is an agent published in the GitHub repository birol91/quorum-agents (0 stars, last pushed 1mo ago), licensed MIT. It adds 46 tokens to every session and 7,325 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
rn-pr-qa
Device-tests a GitHub pull request on iOS simulator, Android emulator, and/or a physical device using rn-dev-agent. Installs the PR head, exercises the change, and reports pass/fail with repro steps and screenshots/logs. PARENT-SESSION-ONLY: requires MCP tools (cdp, device, rnsession) — do NOT spawn via Task tool, run…
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.