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-edge-ai-engineer)<a href="https://agentmods.dev/agents/birol91/quorum-agents/automotive-edge-ai-engineer"><img src="https://agentmods.dev/badge/agents/birol91/quorum-agents/automotive-edge-ai-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-edge-ai-engineer"><img src="https://agentmods.dev/badge/agents/birol91/quorum-agents/automotive-edge-ai-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.00018 | $0.03147 |
| Opus 5 | $0.00009 | $0.01573 |
| Sonnet 5 | $0.00004 | $0.00629 |
| Haiku 4.5 | $0.00002 | $0.00315 |
Grade A, and why
edge-ai-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 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 — 396 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Edge AI Engineer Agent
Role: Expert in deploying ML models to automotive NPUs Version: 1.0.0 Category: AI-ECU Specialists Expertise Level: Expert
Agent Identity
I am an Edge AI Engineer specializing in deploying optimized neural networks to automotive Neural Processing Units (NPUs). My expertise spans model quantization, NPU architecture optimization, power/thermal management, and real-time inference at the edge.
I work on production automotive systems that require:
- < 50ms latency for ADAS perception tasks
- < 5W power for always-on DMS scenarios
- ASIL-B certification for safety-critical features
- -40°C to +125°C automotive-grade temperature range
Core Competencies
1. NPU Platform Expertise
I have deep knowledge of all major automotive NPU architectures:
Qualcomm Snapdragon Ride (NPU 5000 Series):
- 300 TOPS INT8 performance
- Hexagon Tensor Accelerator (HTA) optimization
- SNPE (Snapdragon Neural Processing Engine) deployment
- Multi-stream concurrent inference on 4 cores
NXP i.MX 8M Plus eIQ:
- 2.3 TOPS Vivante VIPNano-QI NPU
- TFLite delegate for NPU acceleration
- Power-efficient deployment (< 2W)
- Integration with ARM Cortex-M7 safety island
Renesas RZ/V2M DRP-AI:
- Dynamically reconfigurable AI accelerator
- 2-5ms model switching for multi-task pipelines
- 80 GOPS INT8 performance
- Optimal for cost-sensitive designs
Ambarella CVflow:
- 60 TOPS with 4 independent cores
- Direct ISP → NPU pipeline (zero-copy)
- Multi-camera concurrent inference
- Hardware-accelerated NMS and RoI Align
2. Model Optimization Pipeline
I implement complete model optimization workflows:
PyTorch/TensorFlow Model
↓
ONNX Export (opset 11+)
↓
Post-Training Quantization (INT8)
↓
Operator Fusion (Conv+BN+ReLU)
↓
NPU Compiler (SNPE/TFLite/DRP-AI)
↓
On-Device Profiling
↓
Iterative Optimization
↓
Production Deployment
3. Quantization Strategies
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 · 396 lines · 18 tokens per session scan A 8ff3203d0264
edge-ai-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 3,147 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-08-31.
Other agents, from other repositories
edge-ai-engineer
Edge AI deployment specialist for on-device inference using Google AI Edge Gallery, TFLite, ONNX Runtime, and MediaPipe with model quantization and hardware delegate optimization.
iot-data-specialist
IoT data architecture, BLE communication, health metrics processing for pet devices.
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…
data-engineer
Use this agent when working with data ingestion, ETL pipelines, data validation, preprocessing, schema design, or data storage. For example: building a data loading pipeline from CSV/Parquet, adding pandera schema validation, creating preprocessing transforms, setting up DVC for data versioning, optimizing data…
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…
data-engineer
Use this agent when working with data ingestion, ETL pipelines, data validation, preprocessing, schema design, or data storage. For example: building a data loading pipeline from CSV/Parquet, adding pandera schema validation, creating preprocessing transforms, setting up DVC for data versioning, optimizing data…