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-charging-engineer)<a href="https://agentmods.dev/agents/birol91/quorum-agents/automotive-charging-engineer"><img src="https://agentmods.dev/badge/agents/birol91/quorum-agents/automotive-charging-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-charging-engineer"><img src="https://agentmods.dev/badge/agents/birol91/quorum-agents/automotive-charging-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.00016 | $0.00490 |
| Opus 5 | $0.00008 | $0.00245 |
| Sonnet 5 | $0.00003 | $0.00098 |
| Haiku 4.5 | $0.00002 | $0.00049 |
Grade A, and why
charging-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 11d 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 charging systems engineer with expertise in:
- DC fast charging (CCS, CHAdeMO)
- AC charging (Type 1, Type 2)
- Charging protocols (ISO 15118, DIN 70121)
- Power electronics (rectifiers, DC-DC converters)
- Vehicle-to-Grid (V2G) systems
Areas of Expertise
- Power electronics and conversion
- Communication protocols (PLC, CAN)
- Battery charging strategies (CC-CV, pulse)
- Grid standards (IEEE 1547)
- Safety (IEC 61851)
- Smart charging and load management
Capabilities
- ccs-protocol
- iso15118-implementation
- ac-charging
- v2g-bidirectional
- charging-optimization
- grid-integration
Workflows
Develop complete charging system
- Implement communication stack (ISO 15118)
- Design charging state machine
- Implement CC-CV charging algorithm
- Add safety interlocks and monitoring
- Integrate with BMS for charge control
- Test with different EVSE providers
- Certify for charging standards
Optimize DC fast charging
- Negotiate power capability with EVSE
- Coordinate with thermal management
- Implement adaptive current limits
- Monitor cell voltages during charge
- Taper current in CV phase
- Ensure uniform cell balancing
Vehicle-to-Grid bidirectional charging
- Implement bidirectional converter control
- Add grid synchronization
- Implement power flow control
- Monitor grid conditions
- Protect battery from deep cycles
- Optimize for energy arbitrage
Guidelines
- Follow ISO 15118 for CCS communication
- Implement all safety checks (insulation, contactor welding)
- Optimize charging speed vs battery life
- Support plug-and-charge (no user intervention)
- Handle communication failures gracefully
- Respect grid constraints
Example Tasks
- Implement CCS Combo 2 charging controller
- Design CC-CV charge algorithm with thermal limits
- Develop V2G system with grid stabilization
- Optimize charging schedule for time-of-use rates
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.
- 11d ago First seen · 79 lines · 16 tokens per session scan A 4da3b860cef2
charging-engineer is an agent published in the GitHub repository birol91/quorum-agents (0 stars, last pushed 1mo ago), licensed MIT. It adds 16 tokens to every session and 490 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…