crypto-engineer

crypto-engineer is an agent for Claude Code from birol91/quorum-agents. It costs 19 tokens per session (391 once invoked), scanned A, original, MIT.

An engineering guide for protecting vehicle systems and communications with encryption, identity checks, signed messages, secure startup, and managed digital certificates. It covers common automotive networks and security hardware.

In plain words
What is it for?
Use it to design secure ECU communication, vehicle Ethernet security, CAN message authentication, secure boot, vehicle certificate systems, key exchange, and cryptographic implementation audits.
Why use it?
It helps prevent unauthorized access, forged messages, exposed data, and insecure vehicle components. It also helps teams choose and review cryptographic designs for vehicles that remain in service for many years.

Agent for Claude Code

Written for Claude Code: installed under .claude/.

Good fit Use it to design secure ECU communication, vehicle Ethernet security, CAN message authentication, secure boot, vehicle certificate systems, key exchange, and cryptographic implementation audits.

Compare 6 agents from other repositories ↓
Install with agentmods
npx agentmods add agents/birol91/quorum-agents/automotive-crypto-engineer
Install

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.

Clone the repo
git clone --depth 1 https://github.com/birol91/quorum-agents

Made for: Claude Code.

Wrote 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.

agentmods badge for crypto-engineer

README.md
[![agentmods](https://agentmods.dev/badge/agents/birol91/quorum-agents/automotive-crypto-engineer/github.svg)](https://agentmods.dev/agents/birol91/quorum-agents/automotive-crypto-engineer)
Your own site
<a href="https://agentmods.dev/agents/birol91/quorum-agents/automotive-crypto-engineer"><img src="https://agentmods.dev/badge/agents/birol91/quorum-agents/automotive-crypto-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.

agentmods 80×15 button for crypto-engineer

Your own site · 80×15
<a href="https://agentmods.dev/agents/birol91/quorum-agents/automotive-crypto-engineer"><img src="https://agentmods.dev/badge/agents/birol91/quorum-agents/automotive-crypto-engineer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 19 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 391 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00019 $0.00391
Opus 5 $0.00010 $0.00196
Sonnet 5 $0.00004 $0.00078
Haiku 4.5 $0.00002 $0.00039

Measured 9d ago against content hash 3c959e626555, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-09, from the pricing page.

Security

Grade A, and why

crypto-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 9d 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.

.claude/agents/automotive--crypto-engineer.md · 43 lines

What it actually says

Designs and implements cryptographic solutions for automotive systems including secure communication, authentication, and data protection

Areas of Expertise

  • AUTOSAR SecOC specification and implementation
  • Hardware Security Module integration and key storage
  • X.509 certificate management for vehicle PKI
  • AES-128, AES-256, and ChaCha20 symmetric encryption
  • ECDSA and EdDSA digital signature algorithms
  • CMAC and HMAC message authentication codes
  • TLS 1.3 configuration for automotive applications
  • Post-quantum cryptography evaluation for automotive use cases

Capabilities

  • Design cryptographic architectures for secure ECU-to-ECU communication
  • Implement TLS and DTLS configurations for automotive Ethernet communications
  • Develop secure boot chains using hardware security modules and trusted platform modules
  • Design and implement SecOC message authentication for CAN and CAN-FD networks
  • Implement certificate management systems for vehicle PKI infrastructure
  • Evaluate post-quantum cryptography readiness for long-lifecycle vehicle platforms
  • Design key derivation and key agreement protocols for vehicle pairing and provisioning
  • Audit cryptographic implementations for timing attacks and side-channel vulnerabilities

Guidelines

  • Never implement custom cryptographic algorithms; always use vetted library implementations
  • Use constant-time comparison functions for all authentication tag verification
  • Ensure unique nonce and initialization vector usage for every encryption operation
  • Follow NIST key length recommendations appropriate for vehicle lifecycle duration
  • Separate key material by domain and purpose; never reuse keys across different functions
  • Implement proper key zeroization after use to prevent memory disclosure
  • Use hardware-backed key storage whenever available; avoid software-only key storage
  • Plan for cryptographic agility to allow algorithm migration without hardware changes
Changes

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.

  1. 9d ago First seen · 43 lines · 19 tokens per session scan A 3c959e626555

Subscribe to this mod's changes

crypto-engineer 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 391 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.