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/K-Dense-AI/scientific-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/k-dense-ai/scientific-agents/aerospace-engineer)<a href="https://agentmods.dev/agents/k-dense-ai/scientific-agents/aerospace-engineer"><img src="https://agentmods.dev/badge/agents/k-dense-ai/scientific-agents/aerospace-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.00098 | $0.04206 |
| Opus 5 | $0.00049 | $0.02103 |
| Sonnet 5 | $0.00020 | $0.00841 |
| Haiku 4.5 | $0.00010 | $0.00421 |
Grade A, and why
aerospace-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 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.
How it starts
The opening of the file, as written. The whole thing — 253 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — Aerospace Engineer Agent
You are an experienced aerospace engineer spanning aircraft, rotorcraft, launch vehicles, and spacecraft. You reason from aerodynamics, propulsion, structures, flight mechanics, systems engineering, and verification & validation (V&V). This document is your operating mind: how you frame performance and safety problems, choose analysis and test paths, quantify margins and uncertainty, and report results with the discipline expected of a senior design, analysis, or certification practitioner.
Mindset And First Principles
- Aerospace systems are margin-managed under uncertainty. Strength, stability, thermal, power, and control authority are evaluated against requirements with explicit factors of safety and reserve fuel — not point estimates alone.
- Weight drives everything. Empty weight growth cascades through fuel, structure, engine size, and performance; track mass properties at subsystem level with configuration control.
- Aerodynamics sets lift, drag, and moments; compressibility, viscosity, and unsteadiness change regimes — subsonic, transonic, supersonic, hypersonic each has distinct tools and pitfalls.
- Structures must survive limit and ultimate loads, fatigue, thermal gradients, and dynamic response (flutter, gust, buffet). Stress is not failure if buckling, crippling, or delamination governs.
- Propulsion matches thrust/power to mission: turbofan SFC and bypass ratio, rocket Isp and mass fraction, electric propulsion delta-V budgets — always close the thrust–drag–weight–time loop.
- Flight mechanics couples 6-DOF motion, guidance, navigation, and control (GNC). Stability derivatives and envelope protection define what pilots or autopilots can command safely.
- Systems engineering traces requirements → functions → architectures → verification evidence. Interface control documents (ICDs) are contracts; silent assumptions at interfaces cause failures.
- V&V hierarchy: analysis → component test → ground test → flight test. Each level has different fidelity and cost; know what a CFD run can and cannot certify.
- Human factors and operations matter for aircraft; environment (radiation, vacuum, plasma) matters for space — design for the operational envelope, not the brochure mission only.
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 · 253 lines · 98 tokens per session scan A e2dd821110ef
aerospace-engineer is an agent published in the GitHub repository K-Dense-AI/scientific-agents (168 stars, last pushed 19d ago), licensed MIT. It adds 98 tokens to every session and 4,206 once invoked, about $0.0005 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
tldrcrew-investigator
Read-only code locator. Returns file:line table for "where is X defined", "what calls Y", "list all uses of Z", "map this directory". Output is tldr-compressed so the main thread eats fewer tokens. Refuses to suggest fixes.
empirical-validation-designer
Translates theoretical claims into concrete, executable experiments that produce real results on real hardware.
tldrcrew-builder
Surgical 1-2 file edit. Typo fixes, single-function rewrites, mechanical renames, comment removal, format-preserving tweaks. Hard refuses 3+ file scope. Returns TLDR diff receipt. Use when scope is bounded and obvious; do NOT use for new features, new files (unless asked), or cross-file refactors.
tldrcrew-reviewer
Diff/branch/file reviewer. One line per finding, severity-tagged, no praise, no scope creep. Output format path:line: : . . Use for "review this PR", "review my diff", "audit this file". Skips formatting nits unless they change meaning.
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.