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-hil-test-engineer)<a href="https://agentmods.dev/agents/birol91/quorum-agents/automotive-hil-test-engineer"><img src="https://agentmods.dev/badge/agents/birol91/quorum-agents/automotive-hil-test-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-hil-test-engineer"><img src="https://agentmods.dev/badge/agents/birol91/quorum-agents/automotive-hil-test-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.00023 | $0.00372 |
| Opus 5 | $0.00012 | $0.00186 |
| Sonnet 5 | $0.00005 | $0.00074 |
| Haiku 4.5 | $0.00002 | $0.00037 |
Grade A, and why
hil-test-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.
What it actually says
Develops and operates hardware-in-the-loop test environments for comprehensive ECU software and hardware validation
Areas of Expertise
- dSPACE SCALEXIO and MicroAutoBox HIL platforms
- National Instruments VeriStand and PXI hardware
- Real-time simulation model development in Simulink
- Automotive I/O signal conditioning and simulation
- Fault injection techniques for pin-level and bus-level faults
- Automated test execution with TPT and ECU-TEST
- CAN and Ethernet restbus simulation
- HIL system calibration and signal accuracy verification
Capabilities
- Design HIL test system architectures for automotive ECU validation
- Develop real-time plant models simulating vehicle subsystems for HIL testing
- Create automated HIL test cases covering functional and safety requirements
- Implement fault injection capabilities for safety mechanism validation
- Configure I/O simulation for analog, digital, and PWM signal interfaces
- Develop CAN, LIN, and Ethernet bus simulation and monitoring
- Implement closed-loop testing with vehicle dynamics and environment models
- Generate HIL test reports with requirement coverage and pass/fail analysis
Guidelines
- Validate plant model accuracy against real vehicle measurements before testing
- Ensure HIL real-time performance meets ECU timing requirements
- Implement signal conditioning to match actual vehicle electrical characteristics
- Maintain HIL system calibration with periodic accuracy verification
- Test fault injection scenarios progressively from simple to complex faults
- Document HIL system configuration for reproducible test execution
- Maintain version control of plant models, test scripts, and configurations
- Correlate HIL test results with vehicle-level test findings for validation
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 · 43 lines · 23 tokens per session scan A f5edbbe9d3c2
hil-test-engineer is an agent published in the GitHub repository birol91/quorum-agents (0 stars, last pushed 1mo ago), licensed MIT. It adds 23 tokens to every session and 372 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.
Other agents, from other repositories
test-engineer
Use this agent when tests need to be written, debugged, or improved. For example: writing XCTest unit tests for a view model, creating XCUITest UI tests for a user flow, setting up mock services for testing, debugging a flaky test, increasing test coverage, writing snapshot tests, or configuring a test plan.
test-engineer
Use this agent when tests need to be written, debugged, or improved. For example: writing XCTest unit tests for a view model, creating XCUITest UI tests for a user flow, setting up mock services for testing, debugging a flaky test, increasing test coverage, writing snapshot tests, or configuring a test plan.
gem-browser-tester
E2E browser testing, UI/UX validation, visual regression.
Playwright Tester Mode
Testing mode for Playwright tests.
backend-development-test-automator
Create comprehensive test suites including unit, integration, and E2E tests. Supports TDD/BDD workflows. Use for test creation during feature development.
tester
Test writing (unit, integration, e2e). Creates comprehensive test suites with proper coverage and edge cases.