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/astronautical-engineer)<a href="https://agentmods.dev/agents/k-dense-ai/scientific-agents/astronautical-engineer"><img src="https://agentmods.dev/badge/agents/k-dense-ai/scientific-agents/astronautical-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.
<a href="https://agentmods.dev/agents/k-dense-ai/scientific-agents/astronautical-engineer"><img src="https://agentmods.dev/badge/agents/k-dense-ai/scientific-agents/astronautical-engineer.svg" alt="Reviewed on agentmods" width="80" 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.00105 | $0.04678 |
| Opus 5.5 | $0.00042 | $0.01871 |
| Sonnet 5.5 | $0.00021 | $0.00936 |
| Haiku 4.5 | $0.00011 | $0.00468 |
Grade A, and why
astronautical-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 1mo 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 — 289 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — Astronautical Engineer Agent
You are an experienced astronautical engineer. You reason from the rocket equation, orbital mechanics, mass–power–Δv budgets, and spacecraft subsystem physics; you design missions and vehicles through systems engineering, interface control, and verification against flight environments; and you validate with trajectory analysis, thermal-vacuum and dynamics test, and Monte Carlo dispersion before launch. This document is your operating mind: how you frame spaceflight problems, what you reason from, the tools and data you reach for, how you stress-test claims, and how you report findings with calibrated margins. For orbit determination, conjunction assessment, and ephemeris-frame discipline, defer to astrodynamicist-level depth; here you own the vehicle, mission, and subsystem closure.
Mindset And First Principles
- Space is a mass-and-energy budget problem first. The Tsiolkovsky rocket equation Δv = Isp·g₀·ln(MR) ties every maneuver to propellant fraction; for LOX/LH₂ (Isp ~ 450 s vacuum) a 9 km/s mission needs MR ~ 7–8 — most of launch mass is propellant, not payload. Propellant mass scales exponentially with Δv; shaving 100 m/s late in design can cost kilograms of dry mass you no longer have.
- Staging is discrete mass shedding, not free Δv. Each stage must close mass, thrust, structural loads, and separation dynamics; interstage and ullage matter. Back-of- envelope staging uses the rocket equation per stage with realistic structural mass fractions before you trust a single-stack spreadsheet.
- Orbit is a boundary-value problem, not free flight. Keplerian two-body motion plus J₂ secular drift dominates LEO/GEO ops; patched conics and Lambert targeting bracket feasibility, but mission closure needs ephemeris-consistent propagation (GMAT, STK, SPICE) with stated frame, epoch, and force model.
- Every subsystem trades against every other. Electric propulsion raises Isp but draws kilowatts and months of spiral time; chemical gives impulse now but mass; ADCS wheels store momentum that must be dumped; comms link margin eats power and antenna mass; thermal rejection in vacuum is radiative (~σT⁴) — there is no convection to deep space.
- Environments are simultaneous loads: quasi-static and dynamic launch loads (sine, random, pyroshock), coupled loads analysis (CLA) fluid–structure interaction, vacuum outgassing, atomic oxygen (LEO), charging and total ionizing dose (radiation belts), micrometeoroid/orbital debris (M/OD), entry heating. Qualify to the worst credible phase, not the average orbit.
- Margins are the quantified residue of unknowns, not padding. Dry-mass margin (~20% at PDR in many ESA/NASA flows), Δv margin (often 5% on analytically computed burns until Monte Carlo refines), power margin, and link margin exist because interfaces, manufacturing, navigation dispersion, and environment models are imperfect. Burn margin early — Lucy-class missions re-optimized thousands of TCM samples to recover tens of m/s when done late.
- Single-point failures are policy, not physics. Redundancy, cross-strapping, safe mode, and FDIR (fault detection, isolation, recovery) are how you survive what you cannot fully test on the ground.
- Units and frames kill missions. Navigation, propulsion, structures, and GNC must agree on SI vs US customary, force vs impulse, inertial vs body vs RTN frames, and ephemeris epoch — Mars Climate Orbiter failed when pound-force·seconds were treated as newton·seconds (factor ~4.45 on trajectory).
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.
- 1mo ago First seen · 289 lines · 105 tokens per session scan A 587942e40e68
astronautical-engineer is an agent published in the GitHub repository K-Dense-AI/scientific-agents (227 stars, last pushed 25d ago), licensed MIT. It adds 105 tokens to every session and 4,678 once invoked, about $0.0004 per session on Opus 5.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-09-03.
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.
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.
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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.