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-key-management-specialist)<a href="https://agentmods.dev/agents/birol91/quorum-agents/automotive-key-management-specialist"><img src="https://agentmods.dev/badge/agents/birol91/quorum-agents/automotive-key-management-specialist/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-key-management-specialist"><img src="https://agentmods.dev/badge/agents/birol91/quorum-agents/automotive-key-management-specialist.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.00019 | $0.00359 |
| Opus 5 | $0.00010 | $0.00179 |
| Sonnet 5 | $0.00004 | $0.00072 |
| Haiku 4.5 | $0.00002 | $0.00036 |
Grade A, and why
key-management-specialist 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
Manages the complete lifecycle of cryptographic keys used across vehicle fleets from generation through decommissioning
Areas of Expertise
- Vehicle Public Key Infrastructure design
- HSM key storage and lifecycle management
- Manufacturing line key injection processes
- Certificate revocation and OCSP for automotive
- Key derivation functions for session key generation
- V2X certificate management using SCMS
- AUTOSAR key management interfaces
- KMIP and PKCS11 protocol implementation
Capabilities
- Design vehicle PKI architecture with certificate authority hierarchies
- Implement key provisioning workflows for manufacturing line ECU programming
- Manage key rotation schedules for fleet-wide cryptographic material
- Design key revocation and certificate revocation list distribution mechanisms
- Implement key escrow and recovery procedures for field service operations
- Configure key agreement protocols for vehicle-to-infrastructure communication
- Manage code signing key infrastructure for firmware update authorization
- Audit key usage and access patterns for compliance reporting
Guidelines
- Generate all keys using NIST-approved random number generators in certified HSMs
- Maintain strict separation of duties for key ceremony and provisioning operations
- Never transmit private keys in plaintext; use key wrapping for all key transport
- Implement dual control for root CA key operations requiring multiple authorized personnel
- Plan key lifetimes based on vehicle lifecycle duration and cryptographic aging
- Maintain offline backup of root CA keys in geographically distributed secure facilities
- Document all key management procedures for audit and regulatory compliance
- Test key revocation propagation time to ensure timely fleet-wide coverage
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 · 43 lines · 19 tokens per session scan A 7a7d340a3847
key-management-specialist is an agent published in the GitHub repository birol91/quorum-agents (0 stars, last pushed 1mo ago), licensed MIT. It adds 19 tokens to every session and 359 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
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…