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 verify-all-deliverablesgit 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/verify-all-deliverables)<a href="https://agentmods.dev/skills/hkuds/openspace/verify-all-deliverables"><img src="https://agentmods.dev/badge/skills/hkuds/openspace/verify-all-deliverables.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 79 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00020 | $0.00689 |
| Opus 5 | $0.00010 | $0.00345 |
| Sonnet 5 | $0.00004 | $0.00138 |
| Haiku 4.5 | $0.00002 | $0.00069 |
Grade A, and why
verify-all-deliverables 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 5d 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 — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Verify All Deliverables Before Completion
Purpose
This skill prevents premature task completion in multi-deliverable workflows by ensuring every required output file is created, verified to exist with non-zero size, and confirmed before declaring <COMPLETE>.
When to Use
Use this skill when a task requires creating multiple output files (e.g., spreadsheet + document, report + summary, data file + visualization).
Instructions
Step 1: Identify All Deliverables Upfront
CRITICAL CHECKPOINT: Do not proceed to Step 2 until this step produces visible output.
Before starting any file creation, you MUST output a complete deliverable list in this exact format:
REQUIRED DELIVERABLES CHECKLIST:
☐ [filename1.extension] - [brief description]
☐ [filename2.extension] - [brief description]
☐ [filename3.extension] - [brief description]
This checklist must appear as visible text in your output before executing any file creation commands. Track completion by updating checkboxes (☐ → ☑) as each file is created.
Step 2: Create Each Deliverable in Sequence
Execute the creation of each file one at a time. Do not proceed to the next step until the current file creation command has completed.
Step 3: Verify Each File After Creation
After creating each file, immediately verify it exists and has non-zero size:
ls -la [filename.extension]
Expected output should show file size > 0 bytes. If size is 0 or file is missing, troubleshoot before proceeding.
Step 4: Final Verification Before Completion
Before declaring <COMPLETE>, run a final verification of ALL deliverables:
ls -la file1.ext file2.ext file3.ext
Or use a loop for many files:
for file in file1.ext file2.ext file3.ext; do
if [ -s "$file" ]; then
echo "✓ $file exists ($(stat -c%s "$file") bytes)"
else
echo "✗ $file missing or empty"
exit 1
fi
done
Step 5: Only Then Declare Complete
Only output <COMPLETE> after all files have been verified with non-zero size.
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.
- 5d ago First seen · 98 lines · 20 tokens per session scan A d1553ee1aed0
verify-all-deliverables is a skill published in the GitHub repository HKUDS/OpenSpace (7,544 stars, last pushed 26d ago), licensed MIT. It adds 20 tokens to every session and 689 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-09-03.
Other skills, from other repositories
orbit-notion
Open Orbit briefing skill — selected by the Orbit pipeline when Notion is the user's only connected connector, or when the user explicitly scopes their daily digest to Notion. Pulls the past 24 hours of document edits, comments, mentions, and database row changes from the user's authenticated Notion connection and…
box
Box manages cloud files, sharing, search, and metadata.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
recipe-save-email-attachments
Find Gmail messages with attachments and save them to a Google Drive folder.
recipe-bulk-download-folder
List and download all files from a Google Drive folder.
apple-notes
Manage Apple Notes via the memo CLI on macOS (create, view, search, edit).