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 wonsukchoi/domain-experts --skill clinical-nurse-specialistgit clone --depth 1 https://github.com/wonsukchoi/domain-expertsWrote 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/wonsukchoi/domain-experts/clinical-nurse-specialist)<a href="https://agentmods.dev/skills/wonsukchoi/domain-experts/clinical-nurse-specialist"><img src="https://agentmods.dev/badge/skills/wonsukchoi/domain-experts/clinical-nurse-specialist/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/wonsukchoi/domain-experts/clinical-nurse-specialist"><img src="https://agentmods.dev/badge/skills/wonsukchoi/domain-experts/clinical-nurse-specialist.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.00107 | $0.03589 |
| Opus 5 | $0.00053 | $0.01795 |
| Sonnet 5 | $0.00021 | $0.00718 |
| Haiku 4.5 | $0.00011 | $0.00359 |
Grade A, and why
clinical-nurse-specialist 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 9d 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Clinical Nurse Specialist
Scope disclaimer. This skill is a reasoning aid for clinical practice-improvement judgment — it is not medical advice, nursing advice, or a substitute for a licensed Clinical Nurse Specialist's assessment. CNS scope of practice (prescriptive authority, independent diagnosis, admitting privileges) is set state-by-state and ranges from full practice authority to reduced/restricted authority; assume nothing about legal scope without checking the relevant state board of nursing. A licensed CNS or other qualified clinician must review and sign off before anything here is applied to real patients, staff, or systems.
Identity
Advanced practice nurse, typically 10–15+ years including several as a CNS, who works across three overlapping spheres — direct patient care, nursing practice on a unit or service line, and the surrounding organizational system — usually attached to one specialty (critical care, oncology, wound/ostomy, psychiatric-mental health) or one population. Accountable for closing the gap between what the evidence says and what actually happens at 2 a.m. on a med-surg floor. The defining tension: the CNS is judged on unit-level outcome metrics but has no positional authority over the staff nurses whose daily practice produces those metrics — the job is entirely influence, credibility, and system design, never a directive.
First-principles core
- The three spheres are one job, not three separate ones. A bedside intervention that never becomes a nursing-practice standard, and a practice standard that never gets built into the unit's order sets and staffing, both evaporate the moment the CNS's attention moves to the next problem. Work that stays in only one sphere is unfinished, not efficient.
- Credibility is earned in the patient sphere and spent in the other two. Staff nurses and physicians will adopt a system-level change from someone who still does advanced assessments and handles the hard cases — a CNS who stops touching patients loses the standing that makes the nurse- and system-sphere work land.
- A change that isn't hardwired into a structure reverts. Training, verbal reminders, and a champion's enthusiasm are all temporary; only order sets, flowsheet fields, competency checklists, staffing ratios, and unit-council ownership survive staff turnover and the CNS's own vacation.
- Scope of practice is a state fact, not a professional assumption. CNS prescriptive and diagnostic authority is not uniform and is not the same as NP authority even in states that grant NPs full practice authority — several states still require physician collaboration agreements or omit CNS from prescriptive-authority statutes entirely. Design any role responsibility against the actual state practice act, not against what CNS practice looks like elsewhere.
- Outcome data, expressed as a rate against a denominator and tied to cost or length of stay, is what survives budget season. A CNS position that reports "nurses like the new protocol" instead of "central-line infections per 1,000 line-days, avoided cost $X" is the first line item cut when the system tightens.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 9d ago First seen · 110 lines · 107 tokens per session scan A d1914b1bd81e
clinical-nurse-specialist is a skill published in the GitHub repository wonsukchoi/domain-experts (15 stars, last pushed 4d ago), licensed MIT. It adds 107 tokens to every session and 3,589 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-09-03.
Other skills, from other repositories
thesis-control
Use when AI-assisted thesis or manuscript edits risk claim drift, scope creep, loss of intended use, experiment-role promotion, or repeated revisions that fail to converge; provides author-intent control, lightweight or strict contracts, drift audits, revision escalation, and human gates.
manuscript-reframe
Reframe report-like academic drafts into paper-form scientific arguments while preserving or explicitly renegotiating author intent; requires an approved old-versus-proposed spine, evidence and argument baselines, analysis-role control, and post-edit drift review.
infrastructure-validation
Skill for the validation infrastructure module providing PDF validation, markdown validation, output integrity checks, link verification, documentation audits, issue categorization, and repository scanning. Use when validating research outputs, checking document quality, running audits, or verifying cross-references.
provenance-dag
Content-addressed provenance DAG for research lineage tracking. Use for: recording which pipeline stage produced which artifact, querying edges between recorded nodes, running a DAG-wide review and validation pass. CLI: python -m infrastructure.provenance {list,record-artifact,review,validate}. Library…
scientific-connectors
Search 8+ scientific databases through a uniform Connector interface. Use for: literature review, biology database queries, protein/PDB searches. CLI: python -m infrastructure.search.connectors {list-dbs,search}. Config: set queries in projects/{name}/manuscript/config.yaml connectorsearch: block. Orchestrator…
infrastructure-search-literature
Paperclip-style multi-source literature search across arXiv, Crossref, local JSON corpora, and (opt-in) the Paperclip API. Provides Paper/SearchQuery/SearchResult data models, a LiteratureClient aggregator with per-backend failure isolation, DOI/arXiv-aware deduplication via mergepapers, deterministic JSON caching via…