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 spreadsheet-proof-gate-merged-fedf41git 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/spreadsheet-proof-gate-merged-fedf41)<a href="https://agentmods.dev/skills/hkuds/openspace/spreadsheet-proof-gate-merged-fedf41"><img src="https://agentmods.dev/badge/skills/hkuds/openspace/spreadsheet-proof-gate-merged-fedf41/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/spreadsheet-proof-gate-merged-fedf41"><img src="https://agentmods.dev/badge/skills/hkuds/openspace/spreadsheet-proof-gate-merged-fedf41.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.00038 | $0.03940 |
| Opus 5 | $0.00019 | $0.01970 |
| Sonnet 5 | $0.00008 | $0.00788 |
| Haiku 4.5 | $0.00004 | $0.00394 |
Grade A, and why
spreadsheet-create-verify-gate 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 — 537 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spreadsheet Create/Verify Gate
Use this skill when you must create from scratch or modify an Excel workbook and the result must be proven against a user specification rather than merely described.
This skill extends the spreadsheet-proof-gate methodology with explicit support for:
- Workbook creation from scratch (not just editing existing files)
- openpyxl-specific pitfall handling (MergedCell, worksheet creation, formula handling)
- Tool failure resilience with clear escalation paths
- Pre-edit audit phases that catch common openpyxl errors before they occur
This is a workflow skill requiring a direct Python verification pass with openpyxl before reporting success. The verification script must be saved to a .py file and executed via run_shell (NOT execute_code_sandbox).
When to use
Use this skill when ANY of the following are true:
Creation scenarios:
- You must create a new Excel workbook from scratch
- No existing template is provided
- You need to establish the initial workbook structure
Editing scenarios:
- The workbook path must be discovered
- Multiple similar Excel files may exist
- The user requires exact sheet names, columns, counts, or samples
- Prior summaries are inconsistent or not trustworthy
- Exact post-edit workbook state matters
General:
- You must prove that mandatory criteria were satisfied
- A delegated agent may perform spreadsheet work
- Tool instability has been observed in prior attempts
Core rules
Rule 1: Creation vs. Editing distinction
Before starting, determine which path applies:
Creation path (new workbook):
- No existing workbook at the target path
- You are establishing the initial structure
- Pre-edit audit focuses on workspace validation and structure planning
Editing path (existing workbook):
- Existing workbook at the target path
- You are modifying structure or content
- Pre-edit audit includes full workbook structure inspection
Rule 2: Openpyxl pitfall awareness
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 · 537 lines · 38 tokens per session scan A db231cbdd4b5
spreadsheet-create-verify-gate is a skill published in the GitHub repository HKUDS/OpenSpace (7,544 stars, last pushed 27d ago), licensed MIT. It adds 38 tokens to every session and 3,940 once invoked, about $0.0002 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
define-data
Standalone Phase 4 of SAP UI testing. Authors one tests/ /test-cases/TC-XXX.data.md requirement spec per case marked dataRequired: yes — choosing the narrowest correct source (sql/static/generated/seeded), and generating upload fixtures in the EXACT file format the program parses (xlsx vs csv). Validates that every…
icedq-mapping-doc-rules
Uses a mapping document provided by the user (Excel, CSV, or Word source-to-target mapping specification) to identify and generate iceDQ rules — Validation, Duplicate, Checksum, Recon, and Pushdown. Use whenever the user uploads or points to a mapping doc or ETL mapping sheet and wants rules derived from it, e.g.…
xz-cases
A generator for acceptance-test checklists covering the core feature changes between specified software versions. It writes the checklist to an XLSX spreadsheet, a format used by Microsoft Excel and similar programs.
postman-test-implementation
Converts an approved company-format testcase workbook (from api-test-design + company-testcase-format) into one Postman collection and one Postman environment, using conventions learned from real company artifacts and this project's src/postman builders. Does not execute anything and does not decide what to test.
company-testcase-format
Formats scenarios produced by api-test-design into the company's real QA testcase conventions (spreadsheet columns, TCID scheme, Postman naming/scripting), learned from actual SDA V2 reference artifacts and kept service-agnostic — never copies SDA's API fields/values into another service's testcase sheet.
test-case-generator
Generates comprehensive, structured test cases from feature descriptions, user stories, requirements, or acceptance criteria — and exports them as a formatted Excel (.xlsx) file ready for use in Excel or Google Sheets. Use this skill whenever the user mentions: "write test cases", "generate test cases", "create test…