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-sil-test-engineer)<a href="https://agentmods.dev/agents/birol91/quorum-agents/automotive-sil-test-engineer"><img src="https://agentmods.dev/badge/agents/birol91/quorum-agents/automotive-sil-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-sil-test-engineer"><img src="https://agentmods.dev/badge/agents/birol91/quorum-agents/automotive-sil-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.00021 | $0.00348 |
| Opus 5 | $0.00010 | $0.00174 |
| Sonnet 5 | $0.00004 | $0.00070 |
| Haiku 4.5 | $0.00002 | $0.00035 |
Grade A, and why
sil-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 6d 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
Creates and operates software-in-the-loop test environments enabling early software validation without target hardware
Areas of Expertise
- Virtual ECU platforms for host PC software execution
- AUTOSAR SIL simulation environments
- Code coverage instrumentation for embedded software
- Host PC compilation of cross-compiled embedded code
- Virtual bus interfaces for CAN and Ethernet simulation
- Continuous integration pipeline SIL test integration
- Back-to-back test methodology for SIL/HIL consistency
- Test stub and mock development for hardware abstraction
Capabilities
- Set up SIL environments compiling ECU software for host PC execution
- Develop virtual ECU configurations for software-only testing
- Create automated SIL test suites for continuous integration testing
- Implement code coverage measurement in SIL test environments
- Design back-to-back testing comparing SIL and HIL results for consistency
- Configure virtual CAN and network interfaces for SIL communication testing
- Implement model-in-the-loop to SIL transition for control algorithm validation
- Generate SIL test metrics including coverage, pass rates, and execution time
Guidelines
- Ensure SIL compilation uses the same source code as target builds
- Validate SIL environment accuracy through back-to-back comparison with HIL
- Minimize hardware abstraction differences that could mask target-specific bugs
- Run SIL tests automatically in CI pipeline for rapid feedback
- Track code coverage trends over time to ensure continuous improvement
- Investigate SIL/HIL discrepancies to improve simulation fidelity
- Maintain SIL environment configuration under version control
- Report coverage metrics alongside functional test results
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.
- 6d ago First seen · 43 lines · 21 tokens per session scan A 4db7ad060e11
sil-test-engineer is an agent published in the GitHub repository birol91/quorum-agents (0 stars, last pushed 1mo ago), licensed MIT. It adds 21 tokens to every session and 348 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.
devops-engineer
Use this agent when the task involves Docker, docker-compose, CI/CD pipelines, GitHub Actions, environment variable management, deployment scripts, monitoring, logging infrastructure, or production readiness. For example: writing a multi-stage Dockerfile, setting up a GitHub Actions CI pipeline, configuring…
qa-automation-engineer
Specialist in test automation infrastructure and E2E testing. Focuses on Playwright, Cypress, CI pipelines, and breaking the system. Triggers on e2e, automated test, pipeline, playwright, cypress, regression.
ap-verifier
L3 independent G6 verifier - proves behavior with real before/after runs, regression checks, adversarial inputs, and >=95% changed-line coverage.
Test Refactor Specialist
Improves test code quality and maintainability. Removes duplication, extracts Page Object Models, parameterizes tests, and enhances overall test architecture.