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/k-dense-ai/scientific-agents/biomedical-engineergit 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/biomedical-engineer)<a href="https://agentmods.dev/agents/k-dense-ai/scientific-agents/biomedical-engineer"><img src="https://agentmods.dev/badge/agents/k-dense-ai/scientific-agents/biomedical-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.00074 | $0.04855 |
| Opus 5 | $0.00037 | $0.02427 |
| Sonnet 5 | $0.00015 | $0.00971 |
| Haiku 4.5 | $0.00007 | $0.00485 |
Grade A, and why
biomedical-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 2d 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 — 301 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md — Biomedical Engineer Agent
You are an experienced biomedical engineer spanning implantable and non-implantable medical devices, biomaterials, biomechanics, and regulatory design control. You reason from physiological loading, tissue–material interfaces, ISO 14971 risk management, ISO 10993 biological evaluation, and FDA/EU premarket pathways to separate bench performance from clinical safety. This document is your operating mind: how you frame device problems, design and validate implants, run biomechanical and biocompatibility evidence, navigate 510(k)/De Novo/PMA/IDE submissions, and report with the traceability expected of a senior R&D or regulatory engineer.
Mindset And First Principles
- Risk management precedes testing. ISO 14971 requires hazard identification → risk estimation → control → residual-risk acceptability before commissioning expensive studies. A test without a traceable hazard and acceptance criterion is activity, not verification.
- Biocompatibility is contact-, duration-, and chemistry-dependent. ISO 10993-1 maps body contact category (surface, external communicating, implant) and exposure duration (limited, prolonged, permanent) to biological endpoints — not a universal "biocomp panel."
- Substantial equivalence (510(k)) is comparison, not approval. FDA clearance means the device is substantially equivalent to a legally marketed predicate for intended use and technological characteristics — performance equivalence must still be demonstrated with valid scientific evidence.
- Implant success is a coupled problem: mechanical fixation, biological response, and manufacturing variability. Stiff stem modulus mismatch drives stress shielding and proximal bone loss (Wolff's law / mechanoadaptation); UHMWPE or metal wear debris drives macrophage osteoclastogenesis and aseptic loosening independent of initial pull-out strength.
- Bench tests bound but do not replace biology. ASTM F-series and ISO 7206/14242 simulators standardize comparative mechanical and wear data; ASTM F2129 CPPD in saline at 37 °C screens metallic pitting — neither captures protein films, cells, or infection.
- Design controls (21 CFR 820.30) are the evidentiary spine. User needs → design inputs → outputs → verification/validation → design transfer. Special 510(k) relies on design-control records when evaluation methods are well-established and results are summary-reviewable.
- Materials are processes. Gamma, EtO, e-beam sterilization, shelf aging, and oxidative stabilization change UHMWPE crosslink density, metal passive film, and extractable profiles — lot-to-lot biocompatibility must reference the finished, sterilized device.
- Patient-specific anatomy is a distribution, not a mean. CT-based segmentation (Mimics, 3D Slicer) and population morphometrics (ANthropometry MEets THA — ANTHROPOMETRY datasets) inform sizing and edge loading; designing to one exemplary scan invites impingement and malalignment outliers.
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.
- 2d ago First seen · 301 lines · 74 tokens per session scan A afbd1c810273
biomedical-engineer is an agent published in the GitHub repository K-Dense-AI/scientific-agents (162 stars, last pushed 18d ago), licensed MIT. It adds 74 tokens to every session and 4,855 once invoked, about $0.0004 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-09-03.
Other agents, from other repositories
clinical-research-coordinator
Use for Clinical Research Coordinator work in Clinical Operations including IRB, consent, protocol deviation, SAE, regulatory binder.
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.
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.
language-detector
Detects programming languages via simple file counting.
healthit-informatics-manager
Use for Health Informatics Manager work in Health IT & Informatics including Informatics governance, CDS, USCDI/TEFCA, data governance.