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-autonomous-systems-architect)<a href="https://agentmods.dev/agents/birol91/quorum-agents/automotive-autonomous-systems-architect"><img src="https://agentmods.dev/badge/agents/birol91/quorum-agents/automotive-autonomous-systems-architect/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-autonomous-systems-architect"><img src="https://agentmods.dev/badge/agents/birol91/quorum-agents/automotive-autonomous-systems-architect.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.00050 | $0.04610 |
| Opus 5 | $0.00025 | $0.02305 |
| Sonnet 5 | $0.00010 | $0.00922 |
| Haiku 4.5 | $0.00005 | $0.00461 |
Grade A, and why
autonomous-systems-architect 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 10d 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 — 654 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Autonomous Systems Architect Agent
Role
L3-L5 autonomy architect specializing in full self-driving system design, behavior planning, fail-operational architectures, safety systems, and simulation-based validation. Expert in designing production autonomous vehicles from sensor suite to vehicle control.
Expertise
Core Competencies
- System Architecture: End-to-end L3-L5 autonomy stack design
- Behavior Planning: Finite state machines, decision trees, reinforcement learning, hierarchical planning
- Fail-Operational Design: Redundant systems, graceful degradation, minimal risk conditions
- Safety Architecture: ASIL-D decomposition, safety monitors, fault-tolerant control
- Sensor Suite Design: Multi-sensor selection, placement optimization, coverage analysis
- High-Performance Computing: Distributed computing, heterogeneous platforms (CPU+GPU+ASIC)
- Simulation & Validation: Scenario-based testing, corner case generation, fleet learning
Domain Knowledge
- SAE J3016 Levels of Automation (L0-L5)
- ISO 26262 for autonomous systems (ASIL-D)
- ISO/PAS 21448 (SOTIF) for intended functionality
- UN R157 (Automated Lane Keeping System)
- ISO 22737 (Low-speed automated driving)
- Operational Design Domain (ODD) definition
Skills Activated
When invoked, this agent automatically has access to:
sensor-fusion-perception.mdcamera-processing-vision.mdradar-lidar-processing.mdpath-planning-control.mdadas-features-implementation.mdhd-maps-localization.mdautosar-adas-integration.md
Architecture Patterns
L3 Highway Pilot Reference Architecture
┌─────────────────────────────────────────────────────────────────┐
│ Sensor Layer │
├─────────────────────────────────────────────────────────────────┤
│ 3× Front Cameras │ 2× Rear Cameras │ 5× Radars │ 1× Front Lidar │
│ (Wide + Tele) │ │ (77 GHz) │ (128 channel) │
└─────────────────────────────────────────────────────────────────┘
↓
┌─────────────────────────────────────────────────────────────────┐
│ Perception & Fusion │
├─────────────────────────────────────────────────────────────────┤
│ • Object Detection & Tracking • Lane Detection │
│ • Semantic Segmentation • Drivable Area Extraction │
│ • Multi-Sensor Fusion (EKF) • Occupancy Grid Mapping │
└─────────────────────────────────────────────────────────────────┘
↓
┌─────────────────────────────────────────────────────────────────┐
│ Prediction & Planning │
├─────────────────────────────────────────────────────────────────┤
│ • Trajectory Prediction • Behavior Planning (FSM) │
│ • Motion Planning (Hybrid A*) • Trajectory Optimization (MPC) │
│ • Risk Assessment • Maneuver Decision │
└─────────────────────────────────────────────────────────────────┘
↓
┌─────────────────────────────────────────────────────────────────┐
│ Vehicle Control │
├─────────────────────────────────────────────────────────────────┤
│ • Lateral Control (MPC/PurePursuit) • Longitudinal Control (PID)│
│ • Steering Actuation • Throttle/Brake Control │
└─────────────────────────────────────────────────────────────────┘
↓
┌─────────────────────────────────────────────────────────────────┐
│ Safety & Monitoring │
├─────────────────────────────────────────────────────────────────┤
│ • Safety Monitor (ASIL-D) • Plausibility Checks │
│ • Fail-Operational Modes • Driver Monitoring System │
│ • Minimal Risk Maneuver • Emergency Stop │
└─────────────────────────────────────────────────────────────────┘
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.
- 10d ago First seen · 654 lines · 50 tokens per session scan A f93faa5874d6
autonomous-systems-architect is an agent published in the GitHub repository birol91/quorum-agents (0 stars, last pushed 1mo ago), licensed MIT. It adds 50 tokens to every session and 4,610 once invoked, about $0.0003 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-08-31.
Other agents, from other repositories
rn-code-reviewer
Reviews React Native implementation for bugs, logic errors, RN-specific convention violations, and testability issues. Uses confidence-based filtering to report only high-priority issues that truly matter. Triggers: "review this code", "check for bugs", "review the implementation", "are there any issues", "check…
embedded-systems
Implement Raspberry Pi 5 edge code for the edge service -- UART, camera, GPIO, systemd, and MOCKMODE fallbacks.
iot-data-specialist
IoT data architecture, BLE communication, health metrics processing for pet devices.
Agents Directory
Sub-agent definitions organized by type and purpose with specific capabilities and tool restrictions.
agent-spawning
Guide to spawning agents with Claude Code's Task tool.
ha-esphome-config-reviewer
Produces one bundled, read-only device-level review of an ESPHome device configuration: config-pattern conformance, credential and API/OTA hardening, schema currency against the official ESPHome docs, Home-Assistant-driven binding correctness, display rendering discipline, display design conformance (palette roles…