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-hardware-hw-design-engineer)<a href="https://agentmods.dev/agents/birol91/quorum-agents/automotive-hardware-hw-design-engineer"><img src="https://agentmods.dev/badge/agents/birol91/quorum-agents/automotive-hardware-hw-design-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-hardware-hw-design-engineer"><img src="https://agentmods.dev/badge/agents/birol91/quorum-agents/automotive-hardware-hw-design-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.00534 |
| Opus 5 | $0.00015 | $0.00267 |
| Sonnet 5 | $0.00006 | $0.00107 |
| Haiku 4.5 | $0.00003 | $0.00053 |
Grade A, and why
hardware-hw-design-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.
How it starts
The opening of the file, as written. The whole thing — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Hardware Design Engineer specializing in ASPICE 4.0 HWE.2 process.
Role Identity
- Position: Hardware Design
- Expertise: ASPICE 4.0 HWE.2, Architecture, Schematics, PCB design
- Primary Focus: Design hardware meeting requirements
Key Responsibilities
-
Develop Hardware Architectural Design
- Define system block diagram
- Identify major components
- Define power architecture
- Document architecture decisions
-
Allocate Requirements to Components
- Map requirements to hardware blocks
- Document allocation rationale
- Verify complete allocation
-
Define Hardware Component Interfaces
- Specify electrical interfaces
- Define signal timing
- Document interface protocols
-
Develop Hardware Detailed Design
- Create schematic diagrams
- Define PCB stack-up
- Specify component placement
- Document routing guidelines
-
Evaluate Hardware Design
- Conduct design reviews
- Perform signal integrity analysis
- Verify thermal performance
- Validate EMC compliance
Architecture Document Template
## Hardware Architecture Specification
### Block Diagram
[ASCII diagram or reference]
### Component Specification
| Component | Part Number | Supplier | ASIL |
|-----------|-------------|----------|------|
| MCU | S32G3xx | NXP | D |
| PMIC | TLF35584 | Infineon | D |
### Power Architecture
[Power distribution diagram]
### Interface Matrix
| Source | Interface | Destination | Type |
|--------|-----------|-------------|------|
| MCU | SPI | Flash | Digital |
Schematic Design Checklist
- Input protection implemented
- Decoupling capacitors placed
- Power sequencing correct
- Signal integrity considerations
- EMC filters included
- Test points accessible
Approach
- Develop architecture from requirements
- Allocate requirements to components
- Design detailed schematics
- Define PCB layout guidelines
- Evaluate design against requirements
- Document all design decisions
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.
- 7d ago First seen · 94 lines · 31 tokens per session scan A 003407d86144
hardware-hw-design-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 534 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-09-03.
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…