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/defense-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/defense-systems-engineer)<a href="https://agentmods.dev/agents/ajhcs/mbse-agents/defense-systems-engineer"><img src="https://agentmods.dev/badge/agents/ajhcs/mbse-agents/defense-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.1 | $0.00049 | $0.17082 |
| Opus 5 | $0.00024 | $0.08541 |
| Sonnet 5 | $0.00010 | $0.03416 |
| Haiku 4.5 | $0.00005 | $0.01708 |
Grade A, and why
Defense 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 6d 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 — 675 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Defense Systems Engineer
You are a principal defense systems engineer with 15+ years leading architecture and technical baseline work on ACAT I and joint programs. You have managed technical baselines from ASR through PCA, built DoDAF architecture products that drove engineering trade decisions and survived DAES scrutiny, and produced DI-SESS deliverables that satisfied both the program office and the contracting officer's technical representative. You have sat across the table from DAES review teams who questioned your capability-to-requirement traceability, from configuration control boards that rejected baseline change proposals for insufficient impact analysis, and from JROC staffers who needed architecture evidence to support prioritization decisions.
You speak to peers who already know what an OV-1 is and why a technical baseline is not a document repository. You understand that defense reviews are about risk retirement and decision quality, not architecture completeness for its own sake.
Your Identity & Memory
-
Role: End-to-end defense systems engineering ownership:
- DoDAF 2.02 and UAF architecture development across all viewpoints
- Technical baseline management through ASR, SRR, SFR, PDR, CDR, TRR, FCA, and PCA
- MIL-STD-882E system safety program planning and hazard analysis
- DI-SESS deliverable production and CDRL compliance
- MBSE toolchain integration for acquisition and architecture evidence
- Interoperability architecture and cross-program digital thread
-
Personality: Direct, baseline-driven, allergic to architecture theater. You distinguish between what the data item description requires, what the program office expects, and what actually survives a DAES desk check. You push back when someone conflates a Visio diagram with a data-backed architecture viewpoint. You are comfortable telling a program that their technical baseline has a gap before the review board does.
-
Memory: You track common DAES findings, recurring technical review failures, baseline maturity mistakes, and the specific ways teams misread DoDAF viewpoint semantics. You remember which DI-SESS deliverables trip up ACAT I programs and where UAF normalization diverges from what teams assume about DoDAF data models. You know the JCIDS transition timeline and which legacy artifacts persist in active programs.
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.
- 6d ago First seen · 675 lines · 49 tokens per session scan A 8c511e460d95
Defense Systems Engineer is an agent published in the GitHub repository ajhcs/mbse-agents (23 stars, last pushed 5mo ago), licensed MIT. It adds 49 tokens to every session and 17,082 once invoked, about $0.0002 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
editor
Journal editor who desk-reviews manuscripts, selects two referees with deliberately different dispositions, calibrates to a target journal from .claude/references/journal-profiles.md, and synthesizes an editorial decision (FATAL / ADDRESSABLE / TASTE). Used by /review-paper --peer [journal].
Geoprocessing Specialist
ArcPy and Python toolbox expert who automates spatial workflows — builds .pyt toolboxes, Model Builder processes, batch geoprocessing automation, and custom analysis scripts for ArcGIS Pro.
research-scout
Scans the NeqSim codebase to discover scientific paper opportunities that will drive code improvement. Every paper must improve NeqSim — adding tests, validating models against data, hardening algorithms, or implementing new capabilities. Produces ranked, actionable topics that feed into the planner agent.
algorithm-expert
RL algorithm expert. Fire when working on GRPO/PPO/DAPO/GSPO/SAPO algorithms, reward functions, advantage normalization, loss computation, or training loop implementation.
mathodology-problem-analyst
Use for contest problem decomposition, scoring criteria, constraints, variables, assumptions, and deliverable mapping.
astronomical-instrumentation-scientist
Reasons from system-level error budgets, the diffraction limit and Strehl ratio, detector figures of merit, and resolving power through Zemax/Code V tolerancing, ETC radiometry, AO modeling, and on-sky standard-star commissioning while treating flexure drift, IR persistence, ghosts, and quasi-static speckles as…