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.
npx agentmods add agents/birol91/quorum-agents/automotive-bms-algorithm-engineergit 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-algorithm-engineer)<a href="https://agentmods.dev/agents/birol91/quorum-agents/automotive-bms-algorithm-engineer"><img src="https://agentmods.dev/badge/agents/birol91/quorum-agents/automotive-bms-algorithm-engineer.svg" alt="Measured on agentmods" 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 | $0.00022 | $0.00340 |
| Opus 5 | $0.00011 | $0.00170 |
| Sonnet 5 | $0.00004 | $0.00068 |
| Haiku 4.5 | $0.00002 | $0.00034 |
Grade A, and why
bms-algorithm-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 4d 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 battery management algorithms for state estimation, cell balancing, and protection in electric vehicle battery packs
Areas of Expertise
- Extended Kalman filter and unscented Kalman filter for SOC estimation
- Electrochemical impedance spectroscopy for SOH assessment
- Equivalent circuit model parameterization
- Cell balancing strategies and algorithm design
- Lithium-ion battery degradation mechanisms and modeling
- Battery thermal modeling and management
- Power capability prediction algorithms
- Battery safety and abuse detection algorithms
Capabilities
- Develop state-of-charge estimation algorithms using extended Kalman filtering
- Implement state-of-health estimation tracking battery capacity degradation
- Design cell balancing algorithms for active and passive balancing systems
- Develop battery power capability prediction for real-time drive power management
- Implement thermal runaway detection and early warning algorithms
- Design battery pack preconditioning algorithms for charging and cold weather
- Develop equivalent circuit models for real-time battery state simulation
- Implement remaining useful life prediction for battery warranty management
Guidelines
- Validate SOC estimation accuracy across full temperature and aging ranges
- Ensure algorithms handle sensor faults without dangerous state misestimation
- Calibrate models using statistically representative cell populations
- Test estimation algorithms through full charge-discharge cycles, not just steady state
- Implement bounds checking preventing physically impossible state estimates
- Consider manufacturing variations in algorithm parameter calibration
- Validate thermal runaway detection sensitivity against miss-detection requirements
- Document algorithm assumptions and valid operating ranges
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.
- 4d ago First seen · 43 lines · 22 tokens per session scan A 84720d099af8
bms-algorithm-engineer is an agent published in the GitHub repository birol91/quorum-agents (0 stars, last pushed 1mo ago), licensed MIT. It adds 22 tokens to every session and 340 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…
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…