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 multi-deliverable-tracking-2eb609git 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/multi-deliverable-tracking-2eb609)<a href="https://agentmods.dev/skills/hkuds/openspace/multi-deliverable-tracking-2eb609"><img src="https://agentmods.dev/badge/skills/hkuds/openspace/multi-deliverable-tracking-2eb609.svg" alt="Measured on agentmods" 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.00024 | $0.00873 |
| Opus 5 | $0.00012 | $0.00436 |
| Sonnet 5 | $0.00005 | $0.00175 |
| Haiku 4.5 | $0.00002 | $0.00087 |
Grade A, and why
multi-deliverable-tracking-2eb609 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 4d 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Multi-Deliverable Tracking
This skill ensures that agents explicitly identify, track, and complete ALL required deliverables before stopping, preventing premature task completion when multiple outputs are required.
Core Principle
Never stop working until you can confirm every required deliverable is complete.
Step-by-Step Instructions
1. Identify All Deliverables Upfront
At the start of any task, explicitly list ALL expected outputs:
## Required Deliverables Checklist
- [ ] Deliverable 1: [description]
- [ ] Deliverable 2: [description]
- [ ] Deliverable 3: [description]
Action: Parse the task description carefully for keywords like:
- "and" (e.g., "create a report AND a presentation")
- "both" (e.g., "both files must be created")
- "each" (e.g., "for each department, create...")
- Numbered requirements (e.g., "1) ..., 2) ...")
- File names mentioned (count them)
2. Track Completion Status
Maintain a visible checklist throughout execution. Update it after each deliverable:
## Progress Tracker
| Deliverable | Status | Evidence |
|-------------|--------|----------|
| Email to CEO | ✅ Complete | File: ceo_email.md created |
| Email to CTO | ⏳ Pending | - |
Action: After completing each item, update the checklist BEFORE moving to the next task.
3. Verify Before Stopping
Before declaring a task complete, perform a final verification:
- Review the original task requirements
- Check each item in your deliverables checklist
- Confirm file existence (use
lsorlist_dirif needed) - Only stop when ALL checkboxes are marked ✅
4. Recovery Protocol
If you discover a missing deliverable:
- Acknowledge the gap: "I notice deliverable X was not completed"
- Prioritize it immediately: Complete the missing item before any other work
- Update the checklist: Mark it complete with evidence
- Re-verify: Ensure no other deliverables were missed
Code Examples
Deliverable Tracking Template
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.
- 4d ago First seen · 119 lines · 24 tokens per session scan A 3c48e0aeab6e
multi-deliverable-tracking-2eb609 is a skill published in the GitHub repository HKUDS/OpenSpace (7,534 stars, last pushed 26d ago), licensed MIT. It adds 24 tokens to every session and 873 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
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
story-readiness
Validate that a story file is implementation-ready. Checks for embedded GDD requirements, ADR references, engine notes, clear acceptance criteria, and no open design questions. Produces READY / NEEDS WORK / BLOCKED verdict with specific gaps. Use when user says 'is this story ready', 'can I start on this story', 'is…
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.