OpenSpace is a skill-management layer for AI agents that stores, retrieves, evaluates, shares, and improves reusable workflows. It is intended for people using multiple coding agents who want skills to be reused and refined based on task outcomes. The catalogue provides 200 skills for use with OpenSpace and the agents it supports.
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 HKUDS/OpenSpace --skill create-soap-note-mergedgit clone --depth 1 https://github.com/HKUDS/OpenSpaceWrote 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/hkuds/openspace/create-soap-note-merged)<a href="https://agentmods.dev/skills/hkuds/openspace/create-soap-note-merged"><img src="https://agentmods.dev/badge/skills/hkuds/openspace/create-soap-note-merged/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/hkuds/openspace/create-soap-note-merged"><img src="https://agentmods.dev/badge/skills/hkuds/openspace/create-soap-note-merged.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00022 | $0.01793 |
| Opus 5.5 | $0.00009 | $0.00717 |
| Sonnet 5.5 | $0.00004 | $0.00359 |
| Haiku 4.5 | $0.00002 | $0.00179 |
Grade A, and why
comprehensive-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 1mo 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 — 210 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Comprehensive SOAP Note Creation
This skill defines the workflow for creating structured medical documentation (SOAP notes) by writing all required sections to a file in one comprehensive operation. This ensures completeness, consistency, and efficiency in clinical documentation.
When to Use
Use this skill when you need to create:
- Medical visit documentation
- Patient encounter records
- Clinical meeting notes
- Healthcare follow-up documentation
that follow the standard SOAP (Subjective, Objective, Assessment, Plan) format.
Objective
Produce a complete medical visit record containing all four SOAP sections without fragmenting the output across multiple files or incomplete drafts. The entire note should be written in a single operation to maintain consistency.
Prerequisites
Before creating the SOAP note, gather:
- Patient demographics: age, gender, patient ID
- Visit details: date, provider name, reason for visit
- Clinical data: vitals, symptoms, exam findings, medical history
- Diagnostic results: labs, imaging (if available)
Core Technique
Write the entire SOAP note in one comprehensive file write rather than building it incrementally. This ensures:
- All sections are complete before writing
- Consistency across the document
- Reduced overhead from multiple write operations
- No risk of partial or fragmented notes
Required Sections
Every SOAP note must include these four components:
1. Subjective (S)
Patient-reported information including:
- Chief Complaint (CC): Patient's primary reason for visit (in their own words when possible)
- History of Present Illness (HPI): Detailed narrative of current symptoms (use OLDCARTS or similar framework: Onset, Location, Duration, Characteristics, Aggravating/Relieving factors, Timing, Severity)
- Past Medical History (PMH): Relevant conditions, surgeries, medications, allergies
- Family History (FH): Pertinent family medical history
- Social History (SH): Relevant social context (occupation, lifestyle, habits)
- Review of Systems (ROS): Systematic symptom review if applicable
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.
- 1mo ago First seen · 210 lines · 22 tokens per session scan A c9afd7755639
comprehensive-soap-note is a skill published in the GitHub repository HKUDS/OpenSpace (7,760 stars, last pushed 2mo ago), licensed MIT. It adds 22 tokens to every session and 1,793 once invoked, about $0.0001 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-08-30.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…