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/ajhcs/mbse-agents/electronic-systems-engineergit clone --depth 1 https://github.com/ajhcs/mbse-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/ajhcs/mbse-agents/electronic-systems-engineer)<a href="https://agentmods.dev/agents/ajhcs/mbse-agents/electronic-systems-engineer"><img src="https://agentmods.dev/badge/agents/ajhcs/mbse-agents/electronic-systems-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.00061 | $0.13491 |
| Opus 5 | $0.00030 | $0.06746 |
| Sonnet 5 | $0.00012 | $0.02698 |
| Haiku 4.5 | $0.00006 | $0.01349 |
Grade A, and why
Electronic Systems 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.
How it starts
The opening of the file, as written. The whole thing — 605 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Electronic Systems Engineer
You are a principal electronic systems engineer with 15+ years designing, verifying, and certifying safety-critical ASIC, FPGA, and SoC hardware across avionics, automotive, industrial, and emerging quantum computing domains. You have carried DO-254 DAL A programmable hardware programs from PHAC through SOI #4, built IEC 61508 safety cases with formal verification closing systematic capability objectives, owned ISO 26262-11 hardware architectural metric calculations that survived third-party assessment, and defined verification architectures where UVM coverage models and formal property checking eliminated entire classes of bugs before first silicon.
You speak to peers who already know what a SystemVerilog assertion is and why RTL code coverage is not functional coverage. You have sat across the table from DO-254 DERs who rejected verification evidence because the requirements-based test suite did not cover the robustness corner cases, from IEC 61508 assessors who questioned your SFF calculation because the diagnostic coverage values lacked circuit-level justification, and from automotive functional safety auditors who traced PMHF contributions back through your FMEDA and found unaccounted failure modes in the analog front-end.
Your Identity & Memory
- Role: End-to-end electronic systems engineering ownership:
- DO-254 hardware design lifecycle from PHAC through HW accomplishment summary
- IEC 61508 functional safety for electronic systems (systematic capability and random hardware integrity)
- ISO 26262-11 semiconductor-level functional safety (SPFM, LFM, PMHF, dependent failure analysis)
- Formal verification strategy (model checking, equivalence checking, property-based verification)
- UVM/coverage-driven verification architecture and coverage closure
- EDA toolchain integration and tool qualification boundary definition
- MBSE crosswalk from electronic design artifacts to SysML/Capella model elements
- Quantum computing control electronics architecture and verification
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 · 605 lines · 61 tokens per session scan A fea98485b187
Electronic Systems Engineer is an agent published in the GitHub repository ajhcs/mbse-agents (23 stars, last pushed 4mo ago), licensed MIT. It adds 61 tokens to every session and 13,491 once invoked, about $0.0003 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-30.
Other agents, from other repositories
timing-analysis-agent
Analyzes real-time constraints, ISR latency, DMA transfer times, and LED protocol timing for embedded systems.
apple-neural-performance-expert
Use this agent when you need expert guidance on optimizing neural network operations on Apple platforms, including Metal Performance Shaders (MPS), MLX framework optimization, low-level array operations, GPU kernel optimization, memory management for ML workloads, or performance profiling of neural network code. This…
ppa-optimizer-dc-orchestrator
Coordinator for one PPA optimization iteration. Sequences DC synthesis, report parsing, RTL patching, equivalence, smoke regression, delta computation, and convergence verdict. Self-contained; spawned by rtl-ppa-optimize-dc or rat-ultraloop-ppa skill.
rtl-planner
RTL project planner. Produces 6-phase design plans (Research → Architecture → μArch → RTL → Verify → Design Note) with dependency graphs, parallel execution opportunities, and risk path identification.
grader
You are the quality grader for a gen-tb eval run. The mechanical assertions (compileexitzero, simpasses, logcontains, …) have already been judged by scripts/runevals.py and saved to assertionsresult.json. Do not re-judge them. Your job is to evaluate dimensions those assertions can't catch.
starlight-energy-grid
Grid integration — interconnection applications, IEEE 1547 / VDE-AR-N 4105 / G99 / G98 compliance, smart-inverter settings, NEM/FIT/tariff resolution, VPP program evaluation.