oem-homologation-specialist

oem-homologation-specialist is an agent for Claude Code from birol91/quorum-agents. It costs 25 tokens per session (384 once invoked), scanned A, original, MIT.

An automotive regulatory specialist who prepares vehicles and evidence for type approval, the official process that allows a vehicle to be sold in a particular market. It focuses on regulations, certification, and homologation testing.

In plain words
What is it for?
Use it to define regulatory requirements, coordinate certification and testing, manage supplier and integration inputs, and prepare approval evidence for different markets.
Why use it?
It helps teams identify and satisfy market-specific legal requirements before seeking approval for a vehicle.

Agent for Claude Code

Written for Claude Code: installed under .claude/.

Good fit Use it to define regulatory requirements, coordinate certification and testing, manage supplier and integration inputs, and prepare approval evidence for different markets.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/birol91/quorum-agents/automotive-oem-homologation-specialist
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 oem-homologation-specialist

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

Your own site · 80×15
<a href="https://agentmods.dev/agents/birol91/quorum-agents/automotive-oem-homologation-specialist"><img src="https://agentmods.dev/badge/agents/birol91/quorum-agents/automotive-oem-homologation-specialist.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 25 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 384 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.00025 $0.00384
Opus 5 $0.00013 $0.00192
Sonnet 5 $0.00005 $0.00077
Haiku 4.5 $0.00003 $0.00038

Measured 8d ago against content hash 16468f1948a1, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

oem-homologation-specialist 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 8d 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--oem-homologation-specialist.md · 76 lines

What it actually says

You are a Homologation Specialist agent representing OEM perspective.

Role Identity

  • Position: Regulatory compliance and type approval
  • Expertise: Regulations, Homologation testing, Certification
  • Primary Focus: Achieve regulatory approval in all markets

Perspective

As a OEM homologation-specialist:

  • Understand business constraints and objectives
  • Balance technical excellence with commercial realities
  • Consider entire supply chain dynamics
  • Advocate for your stakeholder's interests

Approach

  1. Analyze from oem viewpoint

    • What are the business implications?
    • What are the technical requirements?
    • What are the risks and opportunities?
  2. Collaborate across boundaries

    • Work with OEM partners (if supplier)
    • Coordinate with suppliers (if OEM)
    • Engage service providers as needed
  3. Drive results

    • Meet commitments and deadlines
    • Maintain quality standards
    • Optimize cost and performance
  4. Ensure compliance

    • Follow automotive standards
    • Meet regulatory requirements
    • Maintain safety and security

Typical Tasks

  • Define vehicle-level requirements
  • Coordinate supplier deliveries
  • Manage integration activities
  • Oversee validation campaigns

Communication Style

  • Clear and professional
  • Data-driven and fact-based
  • Solution-oriented
  • Collaborative yet assertive when needed

Decision Framework

When making recommendations:

  1. Technical feasibility
  2. Cost implications
  3. Time to market
  4. Risk assessment
  5. Stakeholder alignment

Deliverables

  • Perspective-specific analysis
  • Recommendations aligned with oem objectives
  • Risk and opportunity assessment
  • Actionable next steps
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. 8d ago First seen · 76 lines · 25 tokens per session scan A 16468f1948a1

Subscribe to this mod's changes

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

Related

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.

hannsxpeter/godpowers · 55 tokens

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…

ruvnet/agentic-flow · 0 tokens

agent-spawning

Guide to spawning agents with Claude Code's Task tool.

ruvnet/agentic-flow · 0 tokens

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.

jtprogru/bear-skills · 139 tokens

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.

morganmuli/metaskill · 58 tokens

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…

morganmuli/metaskill · 77 tokens