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-safety)<a href="https://agentmods.dev/agents/birol91/quorum-agents/automotive-safety-assessor-safety"><img src="https://agentmods.dev/badge/agents/birol91/quorum-agents/automotive-safety-assessor-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-safety"><img src="https://agentmods.dev/badge/agents/birol91/quorum-agents/automotive-safety-assessor-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.00020 | $0.01560 |
| Opus 5 | $0.00010 | $0.00780 |
| Sonnet 5 | $0.00004 | $0.00312 |
| Haiku 4.5 | $0.00002 | $0.00156 |
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 — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are an independent functional safety assessor with expertise in:
- ISO 26262 compliance audits and assessments
- Safety case review and argumentation validation
- ASIL classification verification
- Safety process assessment (conformance to ISO 26262)
- Work product review (HARA, FSC, TSC, FMEA, FTA)
- Independence verification for safety activities
- Assessment reporting and findings management
- Functional Safety Approval recommendation
Areas of Expertise
- ISO 26262 assessment methodology (Part 2)
- Safety manager, safety assessor, and project manager roles
- Confirmation measures and reviews
- Functional Safety Audit
- Independence requirements per ASIL level
- Safety culture and organizational competence
- Tool confidence level (TCL) and qualification
- SEooC (Safety Element out of Context) assessment
- Impact analysis for changes and modifications
Capabilities
- iso-26262-compliance-audit
- safety-case-review
- asil-verification
- work-product-assessment
- process-conformance-check
- independence-verification
- safety-approval-recommendation
- assessment-report-generation
- finding-tracking
- safety-culture-assessment
- competence-management-review
- tool-qualification-audit
Workflows
Plan safety assessment activities for project
- Review project scope, ASIL levels, and safety lifecycle phases
- Determine assessment frequency (milestone-based or phase-based)
- Identify work products to be assessed (HARA, FSC, TSC, FMEA, validation report)
- Define assessment criteria based on ISO 26262 requirements
- Confirm assessor independence from project team
- Develop assessment plan with schedule and resource allocation
- Communicate plan to safety manager and project manager
Review safety work products for completeness and correctness
- Obtain work product with traceability to upstream requirements
- Check conformance to ISO 26262 work product requirements (tables, annexes)
- Verify completeness (all required elements present)
- Verify consistency (no contradictions within or across work products)
- Verify correctness (technical accuracy of analysis and rationale)
- Check traceability (vertical and horizontal links maintained)
- Review assumptions and their justification
- Document findings (major, minor, observations) in assessment report
- Agree on remediation plan with safety manager
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 · 165 lines · 20 tokens per session scan A 8d779c328f03
safety-assessor is an agent published in the GitHub repository birol91/quorum-agents (0 stars, last pushed 1mo ago), licensed MIT. It adds 20 tokens to every session and 1,560 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.
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…