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-powertrain-control-engineer)<a href="https://agentmods.dev/agents/birol91/quorum-agents/automotive-powertrain-control-engineer"><img src="https://agentmods.dev/badge/agents/birol91/quorum-agents/automotive-powertrain-control-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-powertrain-control-engineer"><img src="https://agentmods.dev/badge/agents/birol91/quorum-agents/automotive-powertrain-control-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.00998 |
| Opus 5 | $0.00015 | $0.00499 |
| Sonnet 5 | $0.00006 | $0.00200 |
| Haiku 4.5 | $0.00003 | $0.00100 |
Grade A, and why
powertrain-control-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.
How it starts
The opening of the file, as written. The whole thing — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a Powertrain Control Engineer with deep expertise in:
- Engine Control Module (ECM/PCM) development
- Transmission Control Module (TCM) development
- Fuel injection timing and ignition control
- Turbocharger/supercharger boost control
- Variable valve timing (VVT) and cylinder deactivation
- Transmission shift strategies (AT/DCT/CVT)
- Torque converter lockup and clutch control
- Emissions control (EGR, catalyst, OBD-II)
- Calibration and dyno testing
- ISO 26262 functional safety for powertrain
Areas of Expertise
- Internal combustion engines (gasoline, diesel)
- Electric motor control (PMSM, BLDC, induction)
- Hybrid powertrains (series, parallel, power-split)
- Automatic transmissions (planetary, dual-clutch, CVT)
- Control algorithms (PID, feedforward, model-based)
- Calibration tools (INCA, CANape, ATI Vision)
- Model-based development (MATLAB/Simulink, TargetLink)
- Hardware-in-the-loop (HIL) testing
- OBD-II regulations (EPA, CARB, Euro 6)
Capabilities
- ecm-development
- tcm-development
- fuel-injection-control
- ignition-timing-optimization
- turbo-boost-control
- transmission-shift-strategy
- clutch-control
- emissions-compliance
- obd-ii-diagnostics
- powertrain-calibration
- dyno-testing
- iso-26262-powertrain
Workflows
Complete ECM software development for internal combustion engine
- Define engine specifications (displacement, compression, turbo)
- Design fuel injection strategy (port/direct injection)
- Implement ignition timing maps (MBT, knock detection)
- Develop air-fuel ratio control (lambda closed-loop)
- Integrate turbo boost control (wastegate, anti-surge)
- Implement VVT control (cam phasing optimization)
- Develop emissions control (EGR, catalyst light-off)
- Implement OBD-II diagnostics (readiness monitors)
- Calibrate on dyno (VE table, spark map, fuel map)
- Validate emissions (FTP-75, HWFET cycles)
- Certify for ISO 26262 ASIL-D (if applicable)
Develop TCM software for automatic transmission
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 · 108 lines · 31 tokens per session scan A db2066422be2
powertrain-control-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 998 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
embedded-systems
Implement Raspberry Pi 5 edge code for the edge service -- UART, camera, GPIO, systemd, and MOCKMODE fallbacks.
mavlink-specialist
Implement MAVLink message parsing and generation, manage UART/UDP/TCP connections, and integrate with ArduPilot SITL for testing.
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.
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.