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-trackinggit 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)<a href="https://agentmods.dev/skills/hkuds/openspace/multi-deliverable-tracking"><img src="https://agentmods.dev/badge/skills/hkuds/openspace/multi-deliverable-tracking.svg" alt="Measured on agentmods" height="20"></a>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.00018 | $0.01279 |
| Opus 5 | $0.00009 | $0.00639 |
| Sonnet 5 | $0.00004 | $0.00256 |
| Haiku 4.5 | $0.00002 | $0.00128 |
Grade A, and why
multi-deliverable-tracking 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 3d 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 — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Multi-Deliverable Task Completion
Purpose
Ensure ALL required outputs are completed before concluding a task, preventing premature task termination when multiple deliverables are required. This skill includes mandatory enforcement steps that MUST be followed.
Core Workflow
Step 1: Identify All Deliverables Upfront
CRITICAL: You MUST complete this step before producing ANY deliverable or taking any other action.
At task start, explicitly enumerate EVERY required output:
- Parse task requirements carefully for action verbs: "create", "generate", "produce", "deliver", "write", "send"
- Count distinct deliverables (files, reports, emails, code modules, analyses, etc.)
- Document this list visibly in working notes
- Note any dependencies between deliverables
MANDATORY OUTPUT FORMAT: Before any other work, output this exact format:
DELIVERABLES_IDENTIFIED:
1. [filename/description] - [brief description]
2. [filename/description] - [brief description]
...
TOTAL_DELIVERABLES: N
Example identification:
Required Deliverables:
1. [ ] Email to Juvoxa CEO
2. [ ] Follow-up analysis report
Total: 2 deliverables
Step 2: Create a Completion Tracker
CRITICAL: This tracker MUST be created and visible throughout task execution.
Maintain a visible checklist throughout task execution:
DELIVERABLE TRACKER
===================
[ ] Deliverable 1: [brief description]
[ ] Deliverable 2: [brief description]
[ ] Deliverable 3: [brief description]
Completed: 0/3
Update this tracker AFTER each deliverable is fully completed (not just started).
Step 2.5: Filesystem Verification [MANDATORY BEFORE COMPLETION]
Before considering any deliverable complete, verify it exists:
- For file deliverables: Use
list_dirorrun_shell(ls/cat) to confirm the file exists - For output deliverables: Verify the output was actually produced in the response stream
- Document verification with:
[✓] filename verified in filesystem
Step 3: Work Through Deliverables Systematically
- Complete each deliverable fully before marking it done
- Update the tracker immediately after completion
- If a deliverable fails, note the failure but continue to others if possible
- Return to failed items after completing others
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.
- 3d ago First seen · 148 lines · 18 tokens per session scan A f0ff3f13b779
multi-deliverable-tracking is a skill published in the GitHub repository HKUDS/OpenSpace (7,510 stars, last pushed 25d ago), licensed MIT. It adds 18 tokens to every session and 1,279 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.