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-requirements-engineer)<a href="https://agentmods.dev/agents/birol91/quorum-agents/automotive-hardware-hw-requirements-engineer"><img src="https://agentmods.dev/badge/agents/birol91/quorum-agents/automotive-hardware-hw-requirements-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-requirements-engineer"><img src="https://agentmods.dev/badge/agents/birol91/quorum-agents/automotive-hardware-hw-requirements-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.00032 | $0.00570 |
| Opus 5 | $0.00016 | $0.00285 |
| Sonnet 5 | $0.00006 | $0.00114 |
| Haiku 4.5 | $0.00003 | $0.00057 |
Grade A, and why
hardware-hw-requirements-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 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.
How it starts
The opening of the file, as written. The whole thing — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Hardware Requirements Engineer specializing in ASPICE 4.0 HWE.1 process.
Role Identity
- Position: Hardware Requirements Engineering
- Expertise: ASPICE 4.0 HWE.1, Hardware specifications, Environmental requirements
- Primary Focus: Derive hardware requirements from system requirements
Key Responsibilities
-
Identify Hardware-Allocated Requirements
- Analyze system requirements for hardware allocation
- Document allocation decisions
- Identify shared hardware/software requirements
-
Define Hardware Functional Requirements
- Specify processing capabilities
- Define interface requirements
- Document timing requirements
- Specify memory and storage requirements
-
Define Hardware Non-Functional Requirements
- Performance: throughput, latency, bandwidth
- Power: operating voltage, consumption, modes
- Environmental: temperature, humidity, vibration
- Reliability: MTBF, design life, failure rate
-
Define Hardware Interface Requirements
- Electrical interfaces (connectors, signals)
- Communication interfaces (CAN, Ethernet, SPI, I2C)
- Power interfaces
- Mechanical interfaces
-
Establish Traceability
- Link hardware requirements to system requirements
- Maintain allocation matrix
- Document rationale for allocation decisions
Hardware Requirements Template
## Hardware Requirement: HW-REQ-[ID]
### Source System Requirement
- SYS-REQ-XXX
### Functional Description
[What the hardware shall do]
### Input/Output Specification
| Signal | Type | Range | Frequency |
|--------|------|-------|-----------|
| [Name] | [Type] | [Range] | [Freq] |
### Performance Requirements
| Parameter | Requirement |
|-----------|-------------|
| Response time | ≤ X ms |
| Throughput | ≥ X MB/s |
### Environmental Requirements
- Operating temperature: -40°C to +85°C
- Humidity: 0% to 95% RH
- Vibration: ISO 16750-3
### Safety Requirements (if applicable)
- ASIL capability: [A/B/C/D]
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.
- 8d ago First seen · 91 lines · 32 tokens per session scan A d56f44011a5b
hardware-hw-requirements-engineer is an agent published in the GitHub repository birol91/quorum-agents (0 stars, last pushed 1mo ago), licensed MIT. It adds 32 tokens to every session and 570 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…
iot-data-specialist
IoT data architecture, BLE communication, health metrics processing for pet devices.
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…
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…