instrument-cluster-engineer

instrument-cluster-engineer is an agent for Claude Code from birol91/quorum-agents. It costs 18 tokens per session (344 once invoked), scanned A, original, MIT.

An engineer for vehicle instrument clusters, the displays that show driving information such as speed, warnings, and fuel or battery status. It covers graphics, display hardware, vehicle signals, safety rules, brightness, and multiple languages.

In plain words
What is it for?
Use it to build digital gauges, warning and indicator logic, trip computers, configurable information screens, startup animations, and driver-display integrations.
Why use it?
It helps turn vehicle data into clear, timely information for drivers while meeting display and safety requirements. It also supports consistent behavior across different screen technologies and lighting conditions.

Agent for Claude Code

Written for Claude Code: installed under .claude/.

Good fit Use it to build digital gauges, warning and indicator logic, trip computers, configurable information screens, startup animations, and driver-display integrations.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/birol91/quorum-agents/automotive-instrument-cluster-engineer
Install

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.

Clone the repo
git clone --depth 1 https://github.com/birol91/quorum-agents

Made for: Claude Code.

Wrote 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.

agentmods badge for instrument-cluster-engineer

README.md
[![agentmods](https://agentmods.dev/badge/agents/birol91/quorum-agents/automotive-instrument-cluster-engineer/github.svg)](https://agentmods.dev/agents/birol91/quorum-agents/automotive-instrument-cluster-engineer)
Your own site
<a href="https://agentmods.dev/agents/birol91/quorum-agents/automotive-instrument-cluster-engineer"><img src="https://agentmods.dev/badge/agents/birol91/quorum-agents/automotive-instrument-cluster-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.

agentmods 80×15 button for instrument-cluster-engineer

Your own site · 80×15
<a href="https://agentmods.dev/agents/birol91/quorum-agents/automotive-instrument-cluster-engineer"><img src="https://agentmods.dev/badge/agents/birol91/quorum-agents/automotive-instrument-cluster-engineer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 18 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 344 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00018 $0.00344
Opus 5 $0.00009 $0.00172
Sonnet 5 $0.00004 $0.00069
Haiku 4.5 $0.00002 $0.00034

Measured 7d ago against content hash 70d5600d6004, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

instrument-cluster-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 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.

.claude/agents/automotive--instrument-cluster-engineer.md · 43 lines

What it actually says

Designs and implements instrument cluster systems providing critical driving information through analog and digital displays

Areas of Expertise

  • Embedded graphics rendering with OpenGL ES and Vulkan
  • CAN signal reception and display processing
  • Warning and tell-tale indicator regulatory requirements
  • TFT LCD and OLED display driver integration
  • Real-time operating systems for cluster applications
  • Instrument cluster functional safety per ISO 26262
  • Display brightness control and ambient light adaptation
  • Multi-language support and localization

Capabilities

  • Develop digital instrument cluster rendering engines with real-time graphics
  • Implement gauge rendering for speedometer, tachometer, and fuel level displays
  • Design warning indicator management with priority-based display logic
  • Implement tell-tale lamp control meeting regulatory visibility requirements
  • Develop trip computer functionality with fuel consumption and distance calculations
  • Design multi-information display interfaces for driver configurable content
  • Implement cluster startup animation and brand identity display sequences
  • Integrate cluster with ADAS information overlay and navigation guidance

Guidelines

  • Ensure safety-critical warnings are always visible regardless of display mode
  • Meet regulatory requirements for tell-tale visibility, color, and positioning
  • Implement redundant display paths for safety-critical information
  • Minimize display latency between CAN signal reception and gauge update
  • Design for readability under direct sunlight and low ambient light conditions
  • Implement display self-test during cluster initialization
  • Handle CAN signal timeout with appropriate default or warning displays
  • Test display rendering across the full operating temperature range
Changes

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.

  1. 7d ago First seen · 43 lines · 18 tokens per session scan A 70d5600d6004

Subscribe to this mod's changes

instrument-cluster-engineer is an agent published in the GitHub repository birol91/quorum-agents (0 stars, last pushed 1mo ago), licensed MIT. It adds 18 tokens to every session and 344 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.