biomedical-engineer

biomedical-engineer is a skill for Claude Code from K-Dense-AI/scientific-agents. It costs 93 tokens per session (4,900 once invoked), scanned A, original, MIT.

A specialist role for developing and assessing medical devices, implants, and related materials. It combines engineering tests, biological safety, risk management, and regulatory evidence for devices used in healthcare.

In plain words
What is it for?
Use it to identify device risks, plan mechanical and wear tests, assess biocompatibility, and organise evidence for healthcare submissions. It can also help reason about implants, tissue interfaces, and design controls.
Why use it?
It helps connect each test to a known hazard and acceptance limit instead of treating testing as proof by itself. It also separates bench performance from clinical safety and accounts for body contact, exposure time, and regulatory requirements.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin. Also seen: mentions AGENTS.md.

Part of the biomedical-engineer plugin — 1 skill, 1 agent shipped together

Good fit Use it to identify device risks, plan mechanical and wear tests, assess biocompatibility, and organise evidence for healthcare submissions. It can also help reason about implants, tissue interfaces, and design controls.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/k-dense-ai/scientific-agents/biomedical-engineer
Install

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.

Any agent
npx skills add K-Dense-AI/scientific-agents --skill biomedical-engineer
Clone the repo
git clone --depth 1 https://github.com/K-Dense-AI/scientific-agents

Made for: Claude Code.

Or install biomedical-engineer, the plugin that ships this one along with the rest of its 1 skill, 1 agent.

Wrote 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.

agentmods badge for biomedical-engineer

README.md
[![agentmods](https://agentmods.dev/badge/skills/k-dense-ai/scientific-agents/biomedical-engineer/github.svg)](https://agentmods.dev/skills/k-dense-ai/scientific-agents/biomedical-engineer)
Your own site
<a href="https://agentmods.dev/skills/k-dense-ai/scientific-agents/biomedical-engineer"><img src="https://agentmods.dev/badge/skills/k-dense-ai/scientific-agents/biomedical-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.

agentmods 80×15 button for biomedical-engineer

Your own site · 80×15
<a href="https://agentmods.dev/skills/k-dense-ai/scientific-agents/biomedical-engineer"><img src="https://agentmods.dev/badge/skills/k-dense-ai/scientific-agents/biomedical-engineer.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 93 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 4,900 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00093 $0.04900
Opus 5.5 $0.00037 $0.01960
Sonnet 5.5 $0.00019 $0.00980
Haiku 4.5 $0.00009 $0.00490

Measured 16d ago against content hash bb2f918cee15, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

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 16d 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.

scientific-agents/biomedical-engineer/skills/biomedical-engineer/SKILL.md · 305 lines

How it starts

The opening of the file, as written. The whole thing — 305 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.

Read the full file on GitHub · 305 lines

Changes

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.

  1. 16d ago First seen · 305 lines · 93 tokens per session scan A bb2f918cee15

Subscribe to this mod's changes

biomedical-engineer is a skill published in the GitHub repository K-Dense-AI/scientific-agents (210 stars, last pushed 14d ago), licensed MIT. It adds 93 tokens to every session and 4,900 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-30.

Related

Other skills, from other repositories

auditing-part11-trails

Generates and verifies 21 CFR Part 11-style audit trails — who/what/when, electronic signatures, and tamper-evidence — for OpenMed pipelines in GxP and clinical-trial (GCP) settings. Use when the user runs OpenMed in a regulated/validated environment and needs an attributable, time-stamped, tamper-evident record of…

maziyarpanahi/openmed · 222 tokens

generating-synthetic-surrogates

Replace detected PHI with realistic, type-matched fake values in OpenMed so clinical notes stay readable and parseable instead of full of [REDACTED] markers. Use when the user wants surrogate names, MRNs, addresses, or dates rather than opaque masks, needs consistent fake identities across a document, must keep notes…

maziyarpanahi/openmed · 145 tokens

shifting-clinical-dates

Apply consistent per-patient date shifting in OpenMed that preserves intervals between events while satisfying HIPAA Safe Harbor's date rule. Use when the user needs to de-identify dates but keep temporal structure for research, shift all dates by the same offset per patient, preserve days-between-events for survival…

maziyarpanahi/openmed · 135 tokens

rem-investigate-org

The steps for investigating an organisation's page, composed after rem-investigate when the subject is under orgs/.

openonion/connectonion · 27 tokens

clinical

Clinical study design, statistical analysis, and regulatory compliance for medical research.

beita6969/ScienceClaw · 1 tokens

oath

Auditing regulatory compliance (SOC2/PCI-DSS/HIPAA/ISO 27001): maps requirements, checks controls, designs audit trails, implements Policy as Code. Use when compliance auditing is needed.

simota/agent-skills · 45 tokens