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-1e842bgit 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-1e842b)<a href="https://agentmods.dev/skills/hkuds/openspace/multi-deliverable-tracking-1e842b"><img src="https://agentmods.dev/badge/skills/hkuds/openspace/multi-deliverable-tracking-1e842b.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 85 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.00028 | $0.00623 |
| Opus 5 | $0.00014 | $0.00311 |
| Sonnet 5 | $0.00006 | $0.00125 |
| Haiku 4.5 | $0.00003 | $0.00062 |
Grade A, and why
multi-deliverable-tracking-1e842b 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 — 96 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Multi-Deliverable Task Tracking
Purpose
This skill ensures that agents working on tasks with multiple required outputs explicitly track which deliverables are complete and prioritize completing ALL required outputs before considering the task finished.
Problem Pattern
Agents often stop after completing the first or partial set of deliverables, even when multiple outputs are explicitly required. This leads to incomplete task execution.
Instructions
Step 1: Identify All Required Deliverables
At the start of any task, explicitly enumerate ALL required outputs:
Required Deliverables Checklist:
- [ ] Deliverable 1: [description]
- [ ] Deliverable 2: [description]
- [ ] Deliverable 3: [description]
Step 2: Track Progress Explicitly
Maintain a visible progress tracker throughout task execution. Update it after each deliverable is completed:
Progress Tracker:
- [x] Email to Juvoxa CEO (COMPLETE)
- [ ] Email to Second Company CEO (PENDING)
Step 3: Verify Before Stopping
Before concluding the task, perform a final verification:
- Review the original task requirements
- Check each item in your deliverables checklist
- Confirm ALL items are marked complete
- Only stop when every required deliverable is finished
Step 4: Prioritize Completion Over Speed
If you encounter difficulties with one deliverable:
- Do NOT abandon remaining deliverables
- Attempt alternative approaches (switch tools, methods, etc.)
- Complete what you can before reporting any blockers
Example Workflow
Task: Create emails to two company CEOs
1. INITIALIZE CHECKLIST:
- [ ] Email to Juvoxa CEO
- [ ] Email to PartnerCo CEO
2. EXECUTE DELIVERABLE 1:
- Create email to Juvoxa CEO
- Save/output the file
- UPDATE: - [x] Email to Juvoxa CEO
3. CHECK STATUS:
- 1 of 2 complete
- Continue to next deliverable
4. EXECUTE DELIVERABLE 2:
- Create email to PartnerCo CEO
- Save/output the file
- UPDATE: - [x] Email to PartnerCo CEO
5. FINAL VERIFICATION:
- All checkmarks complete? YES
- Task is now complete
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 · 96 lines · 28 tokens per session scan A 2ba429dfc7cf
multi-deliverable-tracking-1e842b is a skill published in the GitHub repository HKUDS/OpenSpace (7,544 stars, last pushed 26d ago), licensed MIT. It adds 28 tokens to every session and 623 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.
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…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
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.