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 skills/hkuds/openspace/create-soap-notenpx skills add HKUDS/OpenSpace --skill create-soap-notegit clone --depth 1 https://github.com/HKUDS/OpenSpaceWhat 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 | $0.00021 | $0.00704 |
| Opus 5 | $0.00010 | $0.00352 |
| Sonnet 5 | $0.00004 | $0.00141 |
| Haiku 4.5 | $0.00002 | $0.00070 |
Grade A, and why
create-soap-note 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create SOAP Note
This skill defines the workflow for creating structured medical documentation (SOAP notes) by writing comprehensive content directly to a file. It ensures all standard sections are included and properly formatted.
Objective
Produce a complete medical visit record containing Subjective, Objective, Assessment, and Plan sections without fragmenting the output across multiple files or incomplete drafts.
Prerequisites
- Patient demographic information (age, gender, ID).
- Visit details (date, provider, reason for visit).
- Clinical data (vitals, symptoms, exam findings, history).
Workflow Steps
1. Prepare Content Structure
Organize the note into the four standard SOAP sections. Do not omit any section even if data is sparse (note "not applicable" or "deferred" where appropriate).
2. Draft Comprehensive Content
Write the full content for each section in one continuous operation. Avoid placeholders like [insert here] unless data is genuinely missing and must be flagged for follow-up.
- Subjective (S):
- Chief Complaint (CC)
- History of Present Illness (HPI)
- Past Medical History (PMH)
- Family/Social History (FH/SH)
- Review of Systems (ROS)
- Objective (O):
- Vitals (BP, HR, Temp, Resp, O2 Sat, Weight/Height)
- Physical Exam (by system)
- Diagnostic Results (Labs, Imaging)
- Assessment (A):
- Primary Diagnosis
- Differential Diagnoses
- Problem List
- Plan (P):
- Management/Treatment
- Medications
- Follow-up Instructions
- Patient Education
3. Write to File
Save the complete note to a single file (e.g., soap_note_<patient_id>_<date>.md or .txt). Ensure the file is saved in one write operation to maintain consistency.
4. Review for Completeness
Verify that all four headers exist and contain substantive content.
Template Example
# SOAP Note - [Patient Name] - [Date]
## Subjective
**Chief Complaint:** [Reason for visit]
**HPI:** [Detailed history]
**PMH:** [Conditions, surgeries]
**Social/Family History:** [Relevant details]
## Objective
**Vitals:** [List values]
**Physical Exam:** [Findings by system]
**Labs/Imaging:** [Results]
## Assessment
**Diagnoses:**
1. [Primary Diagnosis]
2. [Differential]
## Plan
**Management:** [Steps taken]
**Medications:** [Prescriptions]
**Follow-up:** [Timeline]
**Education:** [Instructions given]
What ships with it
1 file 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.
- 2d ago First seen · 91 lines · 21 tokens per session scan A b23607f5eede
create-soap-note is a skill published in the GitHub repository HKUDS/OpenSpace (7,486 stars, last pushed 20d ago), licensed MIT. It adds 21 tokens to every session and 704 once invoked, about $0.0001 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
agent-host-chat-contributions
Build and review cross-cutting agent-host chat behavior through lifecycle contributions. Use when adding turn lifecycle side effects, prompt or context injection, restored-history transformation, protocol-action observation, or when reviewing changes that add code to AgentSideEffects or AgentService.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.