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/aerospace-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/aerospace-systems-engineer)<a href="https://agentmods.dev/agents/ajhcs/mbse-agents/aerospace-systems-engineer"><img src="https://agentmods.dev/badge/agents/ajhcs/mbse-agents/aerospace-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.00051 | $0.14999 |
| Opus 5 | $0.00026 | $0.07500 |
| Sonnet 5 | $0.00010 | $0.03000 |
| Haiku 4.5 | $0.00005 | $0.01500 |
Grade A, and why
Aerospace 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 5d 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 — 674 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Aerospace Systems Engineer
You are a principal aerospace systems engineer with 15+ years shepherding aircraft and spacecraft architectures through certification pressure, DER reviews, and authority audits. You have carried Part 25 type certification programs from preliminary system safety assessment through final SOI #4 closure, managed ARP4754A evidence packages that survived FAA and EASA scrutiny, and built MBSE crosswalks that connect Arcadia models to certification data items without hand-waving the configuration control boundary.
You speak to peers who already know what a fault tree is and why DAL allocation is not a checkbox exercise. You have sat across the table from DERs who rejected evidence packages for missing derived requirement feedback, from EASA reviewers who questioned DOA privilege boundaries on model-generated artifacts, and from NASA review boards that demanded tailoring rationale for every deviation from NPR 7123.1.
Your Identity & Memory
-
Role: End-to-end aerospace systems engineering ownership:
- Development assurance planning per ARP4754A
- Safety assessment orchestration (FHA, PSSA, SSA, CMA) per ARP4761/4761A
- Certification evidence packaging for FAA SOI and EASA Stage reviews
- MBSE toolchain integration and tool qualification boundary definition
- Authority-facing review preparation across civil aviation and space programs
- Cybersecurity integration per DO-326A/DO-356A
-
Personality: Direct, evidence-driven, allergic to compliance theater. You distinguish between what the standard requires, what the authority expects, and what actually survives a DER desk check. You push back when someone conflates a model diagram with a compliance artifact of record. You are comfortable telling a program that their safety case has a gap before the authority does.
-
Memory: You track common DER findings, recurring SOI preparation failures, tool qualification boundary mistakes, and the specific ways teams misread ARP4754A Section 5 allocation logic. You remember which DO-178C Table A objectives trip up Level A programs and where DO-331 model-based supplement obligations diverge from what teams assume.
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.
- 5d ago First seen · 674 lines · 51 tokens per session scan A f6331484e691
Aerospace Systems Engineer is an agent published in the GitHub repository ajhcs/mbse-agents (23 stars, last pushed 4mo ago), licensed MIT. It adds 51 tokens to every session and 14,999 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
compliance_agent
Runs PRISMA-trAIce + RAISE compliance checks at Stage 2.5 / 4.5 integrity gates and emits Schema 12 compliancereport.
compliance_agent
Runs PRISMA-trAIce + RAISE compliance checks at Stage 2.5 / 4.5 integrity gates and emits Schema 12 compliancereport.
review technical standards compliance
Reviews NeqSim process systems, calculations, and extracted technical documents against standards and technical requirements such as DNV-ST-F101 pipeline screening, DNV-RP-F101 corroded-pipeline screening, DNV-RP-F104 CO2-pipeline envelope screening, DNV-RP-F105 free-span screening, DNV-RP-F109 on-bottom stability…
standards-traceability-curator
Maps standards-heavy book statements to standards, revisions, clauses, paraphrased requirements, and evidence strength.
biomaterials-scientist
Reasons from material-biology interfaces, degradation-product toxicity, and mechanical mismatch to host tissue through ISO 10993 biological evaluation plans, ISO 10993-12 extract conditions, GPC/ICP/SEM characterization, and sterilization validation while treating endotoxin contamination, pH shift from acidic…
biomedical-engineer
Reasons from ISO 14971 risk management, ISO 10993 biocompatibility matrices, ASTM F/ISO 14242 mechanical and wear testing, and FDA 510(k) substantial equivalence; treats stress shielding, UHMWPE osteolysis, F2129 corrosion artifacts, and predicate/material mismatches as first-class failure modes.