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 skills add iblai/medical-healthcare-agents --skill nuance-daxgit clone --depth 1 https://github.com/iblai/medical-healthcare-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/skills/iblai/medical-healthcare-agents/nuance-dax)<a href="https://agentmods.dev/skills/iblai/medical-healthcare-agents/nuance-dax"><img src="https://agentmods.dev/badge/skills/iblai/medical-healthcare-agents/nuance-dax/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/skills/iblai/medical-healthcare-agents/nuance-dax"><img src="https://agentmods.dev/badge/skills/iblai/medical-healthcare-agents/nuance-dax.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.00037 | $0.00653 |
| Opus 5 | $0.00018 | $0.00327 |
| Sonnet 5 | $0.00007 | $0.00131 |
| Haiku 4.5 | $0.00004 | $0.00065 |
Grade A, and why
nuance-dax 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 12d 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 — 39 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Nuance DAX
What it is
Nuance DAX (Dragon Ambient eXperience) is Microsoft's leading ambient AI documentation platform used by over 550 US health systems. It converts real-time encounter audio into structured clinical note drafts (SOAP, H&P, progress notes, procedure notes) that surface in the EHR In-Basket for clinician review and approval before any note is finalized. DAX Copilot is the current SaaS iteration, integrated natively into Epic and Cerner workflows.
When to use this skill
- Retrieve a completed DAX ambient note draft after a clinical encounter
- Check note generation status for a given encounter ID
- Submit a corrected or amended note segment back into the DAX review queue
- Pull specialty-specific note template configurations (e.g., cardiology H&P vs. primary care SOAP)
- Integrate DAX output with EHR draft note APIs (Epic In-Basket, Cerner PowerNote)
Credentials
This skill authenticates using variables declared in the metadata above. Copy ~/.openclaw/.env.example to ~/.openclaw/.env and fill in real values. Required variables:
NUANCE_DAX_API_KEY- API key issued by Nuance/Microsoft for the facility integrationNUANCE_DAX_BASE_URL- DAX API base URL (facility-specific endpoint provided at onboarding)NUANCE_DAX_FACILITY_ID- facility identifier assigned during DAX deployment
Key operations
GET /encounters/{encounter_id}/note-draft— retrieve generated note draft by encounter IDGET /encounters/{encounter_id}/status— check processing status (queued/processing/complete/failed)POST /encounters/{encounter_id}/corrections— submit clinician correction segment for reprocessingGET /templates— list available specialty note templatesGET /templates/{template_id}— fetch template structure (sections, fields, default text)POST /encounters— register a new encounter session before audio capture begins
Notes
- Note drafts are returned as structured JSON with section-level text; convert to HL7 CDA or FHIR DocumentReference before writing to EHR.
- DAX operates under a BAA with Microsoft/Nuance; all audio and transcription data is encrypted at rest and in transit.
- Audio capture is handled by the DAX mobile app or EHR plugin — this API skill covers server-side note retrieval and integration, not audio streaming.
- Typical processing latency: 2-5 minutes post-encounter; implement polling with exponential backoff.
- Sandbox / test environment credentials are separate from production; never use production keys in development.
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.
- 12d ago First seen · 39 lines · 37 tokens per session scan A b8cef4c3bf99
nuance-dax is a skill published in the GitHub repository iblai/medical-healthcare-agents (10 stars, last pushed 3mo ago), licensed MIT. It adds 37 tokens to every session and 653 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-31.
Other skills, from other repositories
upload-artifact
Upload a file as a ClosedLoop document (PRD, implementation plan, feature, or template). Reads file content and uploads via MCP without consuming conversation context. Also supports creating new versions of existing documents. Triggers on: "upload artifact", "upload PRD", "upload implementation plan", "upload…
extract-plan-md
Sync plan.md with plan.json content. MUST be used after ANY edit to plan.json to keep plan.md in sync. Triggers: After editing plan.json with Edit tool (REQUIRED - always sync after edits) User asks to "sync plan.md", "update plan.md", "extract the md from a plan" Converting plan.json to markdown or viewing plan as…
document-xlsx
Create/edit .xlsx spreadsheets with tables, formulas, charts, validation, and workbook automation. Use when asked to generate Excel reports, models, exports, or audit spreadsheets.
document-docx
Create/edit .docx files with styles, templates, comments, and extraction workflows. Use when asked to generate Word reports, contracts, proposals, or convert Word content.
document-pdf
Extracts, creates, and transforms PDF documents. Use when parsing text or tables, generating files, merging pages, or handling PDF forms.
qa-docs-coverage
Audits and enforces documentation quality. Use when checking coverage, freshness, runbook validity, AI-instruction coverage, or cleaning stale/duplicate markdown after LLM edits.