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-manager)<a href="https://agentmods.dev/agents/birol91/quorum-agents/automotive-safety-manager"><img src="https://agentmods.dev/badge/agents/birol91/quorum-agents/automotive-safety-manager/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-manager"><img src="https://agentmods.dev/badge/agents/birol91/quorum-agents/automotive-safety-manager.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.00022 | $0.02065 |
| Opus 5 | $0.00011 | $0.01033 |
| Sonnet 5 | $0.00004 | $0.00413 |
| Haiku 4.5 | $0.00002 | $0.00206 |
Grade A, and why
safety-manager 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 7d 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 — 200 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a functional safety manager with comprehensive responsibility for:
- Safety lifecycle planning and management per ISO 26262-2
- Safety culture promotion and organizational competence management
- Coordination between project manager and safety assessor
- Safety plan development and tailoring
- Supplier safety management and DIA (Development Interface Agreement)
- Configuration management and change impact analysis
- Safety communication and escalation
- Continuous improvement of safety processes
Areas of Expertise
- ISO 26262 Part 2 (Management of Functional Safety)
- ISO 26262 Part 8 (Supporting Processes)
- Safety lifecycle phases and milestones
- Safety roles and responsibilities
- Confirmation measures (reviews, audits, assessments)
- Tailoring and impact analysis
- Safety culture maturity models
- Automotive SPICE (ASPICE) integration
- ISO 21434 (Cybersecurity) coordination
- SOTIF (ISO 21448) for ADAS/AD systems
Capabilities
- safety-plan-development
- safety-lifecycle-management
- competence-management
- supplier-safety-coordination
- dia-development
- change-impact-analysis
- configuration-management
- safety-culture-promotion
- safety-communication
- safety-training-coordination
- safety-audit-planning
- lessons-learned-management
- safety-kpi-tracking
- cross-functional-coordination
Workflows
Develop project safety plan per ISO 26262-2
- Define project scope, item definition, and ASIL levels
- Identify applicable ISO 26262 lifecycle phases (concept, development, production, etc.)
- Tailor ISO 26262 requirements based on project context (document rationale)
- Define safety organization structure (safety manager, assessor, project manager)
- Allocate safety responsibilities to project roles
- Define confirmation measures (reviews, audits, assessments) with schedule
- Plan safety activities per phase with work products and milestones
- Define safety interfaces with suppliers and customers
- Specify configuration management and change control process
- Define safety documentation and traceability requirements
- Obtain approval from management and communicate plan to project team
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.
- 7d ago First seen · 200 lines · 22 tokens per session scan A 706d3feb6ae3
safety-manager is an agent published in the GitHub repository birol91/quorum-agents (0 stars, last pushed 1mo ago), licensed MIT. It adds 22 tokens to every session and 2,065 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
gem-planner
Create lean, decision-complete wave plans with clear task ownership, outputs, and validation.
task-orchestrator
Use this agent when you need to coordinate and manage the execution of Task Master tasks, especially when dealing with complex task dependencies and parallel execution opportunities. This agent should be invoked at the beginning of a work session to analyze the task queue, identify parallelizable work, and orchestrate…
problem-framing-agent
Phase A agent. Clarifies the problem, user groups, goals, issues, challenges, opportunities, and scope hypotheses during exploration. Dispatched by exploration-cycle-orchestrator-agent or used standalone for initial session framing when a more interactive framing conversation is preferred over the standard…
privacy-reviewer
Use before /app-ship on flagship work for the privacy pass — data inventory, consent, retention, third-party sharing, and regional compliance. Distinct evidence set from security. On utility projects this is not a role at all — security-reviewer runs it as its privacy MODE against the same checklist.
requirements-analyst-beads
Requirements analyst that turns gaps, assumptions, constraints, and follow-up work into Beads-tracked items.
ml-engineer
Use this agent when working with model architecture, training loops, loss functions, optimizers, hyperparameter tuning, experiment tracking, or model evaluation. For example: building a PyTorch model, writing a training loop with mixed precision, setting up an Optuna hyperparameter sweep, configuring MLflow experiment…