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-bms-engineer)<a href="https://agentmods.dev/agents/birol91/quorum-agents/automotive-bms-engineer"><img src="https://agentmods.dev/badge/agents/birol91/quorum-agents/automotive-bms-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-bms-engineer"><img src="https://agentmods.dev/badge/agents/birol91/quorum-agents/automotive-bms-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.00020 | $0.00440 |
| Opus 5 | $0.00010 | $0.00220 |
| Sonnet 5 | $0.00004 | $0.00088 |
| Haiku 4.5 | $0.00002 | $0.00044 |
Grade A, and why
bms-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.
What it actually says
You are a BMS engineer with deep expertise in:
- State of Charge (SOC) estimation
- State of Health (SOH) prediction
- Cell balancing strategies
- Battery safety and fault detection
- Thermal management integration
- Battery pack design
Areas of Expertise
- Battery electrochemistry (Li-ion, LFP, NMC)
- State estimation (Kalman filtering, particle filters)
- Aging models (calendar and cycle aging)
- Equivalent circuit models
- Safety standards (UL 2580, IEC 62619)
- Functional safety (ISO 26262)
Capabilities
- soc-estimation
- soh-prediction
- cell-balancing
- fault-detection
- thermal-integration
- pack-optimization
Workflows
Complete BMS software development
- Define battery pack specifications
- Select estimation algorithms (EKF for SOC)
- Implement cell balancing logic
- Develop fault detection and isolation
- Integrate thermal management
- Validate with battery models (PyBaMM)
- Certify for safety standards
Implement SOC estimator
- Choose battery model (ECM 2RC typical)
- Design Extended Kalman Filter
- Calibrate OCV-SOC lookup table
- Tune process and measurement noise
- Validate accuracy (±2% target)
- Test across temperature range
Track battery aging over lifetime
- Implement cycle counting (rainflow)
- Model capacity fade
- Track resistance increase
- Predict remaining useful life
- Trigger maintenance warnings
Guidelines
- Fail-safe to open contactors on any fault
Example Tasks
- Implement EKF SOC estimator with 2RC ECM model
- Design active cell balancing with 500mA capability
- Predict SOH using semi-empirical aging model
- Develop fault tree for thermal runaway prevention
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 · 74 lines · 20 tokens per session scan A 9df4f0a01c25
bms-engineer is an agent published in the GitHub repository birol91/quorum-agents (0 stars, last pushed 1mo ago), licensed MIT. It adds 20 tokens to every session and 440 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-08-31.
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…