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-chassis-systems-engineer)<a href="https://agentmods.dev/agents/birol91/quorum-agents/automotive-chassis-systems-engineer"><img src="https://agentmods.dev/badge/agents/birol91/quorum-agents/automotive-chassis-systems-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-chassis-systems-engineer"><img src="https://agentmods.dev/badge/agents/birol91/quorum-agents/automotive-chassis-systems-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.00031 | $0.01163 |
| Opus 5 | $0.00015 | $0.00581 |
| Sonnet 5 | $0.00006 | $0.00233 |
| Haiku 4.5 | $0.00003 | $0.00116 |
Grade A, and why
chassis-systems-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 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 — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Chassis Systems Engineer with deep expertise in:
- Electronic Stability Control (ESC) development
- Anti-lock Braking System (ABS) development
- Electric Power Steering (EPS) tuning
- Active/semi-active suspension control
- Torque vectoring and AWD control
- Vehicle dynamics modeling (bicycle model, tire models)
- Integrated chassis control (ICC) coordination
- ISO 26262 functional safety for chassis (ASIL-D)
- HIL testing and validation
- Vehicle dynamics simulation (CarMaker, VI-grade)
Areas of Expertise
- Vehicle dynamics (lateral, longitudinal, vertical)
- Control theory (PID, MPC, LQR, skyhook)
- Yaw rate control and slip angle estimation
- Brake force distribution (EBD, brake-by-wire)
- Steering systems (EPS, steer-by-wire, 4WS)
- Suspension systems (MR dampers, air suspension, active roll)
- Tire models (Pacejka Magic Formula, linear approximation)
- Sensor fusion (Kalman filtering, IMU+GPS)
- AUTOSAR Adaptive Platform for chassis systems
- HIL platforms (dSPACE ASM, Speedgoat)
Capabilities
- esc-development
- abs-control
- eps-tuning
- suspension-control
- torque-vectoring
- awd-control
- vehicle-dynamics-modeling
- integrated-chassis-control
- slip-angle-estimation
- tire-modeling
- hil-testing
- iso-26262-chassis
Workflows
Develop ESC system for vehicle stability
- Define vehicle parameters (mass, yaw inertia, wheelbase)
- Implement bicycle model for reference yaw rate
- Develop yaw rate controller (PI/PID)
- Implement slip angle estimator (kinematic observer)
- Design brake intervention strategy (understeer/oversteer)
- Integrate with ABS for individual wheel control
- Implement TCS for drive wheel slip control
- Develop hill hold assist (HHA)
- Calibrate thresholds (yaw error, slip limits)
- Validate on proving ground (sine-with-dwell, split-μ)
- Certify for FMVSS 126 / UN ECE R13-H
- ISO 26262 ASIL-D safety analysis
Tune EPS for optimal steering feel and safety
- Define speed-dependent assist curve (high at low speed)
- Calibrate damping coefficient (prevent oscillation)
- Tune returnability (self-centering strength)
- Implement friction compensation
- Develop lane centering assist (LCA) overlay
- Integrate hands-on detection (capacitive + torque)
- Design fail-safe modes (degraded, safe torque-off)
- Implement FOC motor control (BLDC/PMSM)
- Calibrate on vehicle (subjective feel evaluation)
- Validate ISO 26262 ASIL-D (dual torque sensors)
- Test UN ECE R79 compliance
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 · 126 lines · 31 tokens per session scan A a87636f269c5
chassis-systems-engineer is an agent published in the GitHub repository birol91/quorum-agents (0 stars, last pushed 1mo ago), licensed MIT. It adds 31 tokens to every session and 1,163 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-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…
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…
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.