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 sandbox-failure-recoverygit 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/sandbox-failure-recovery)<a href="https://agentmods.dev/skills/hkuds/openspace/sandbox-failure-recovery"><img src="https://agentmods.dev/badge/skills/hkuds/openspace/sandbox-failure-recovery/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/sandbox-failure-recovery"><img src="https://agentmods.dev/badge/skills/hkuds/openspace/sandbox-failure-recovery.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.00023 | $0.00892 |
| Opus 5 | $0.00012 | $0.00446 |
| Sonnet 5 | $0.00005 | $0.00178 |
| Haiku 4.5 | $0.00002 | $0.00089 |
Grade A, and why
sandbox-failure-recovery 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 6d 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 — 133 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Sandbox Failure Recovery Workflow
When execute_code_sandbox fails (often due to infrastructure issues, timeouts, or complex dependencies), use this recovery pattern to achieve identical results by writing the code to a file and executing it directly.
When to Use This Skill
execute_code_sandboxreturns an error or times out- The task involves spreadsheet generation (Excel, CSV) or file output
- You have working Python code that needs to be executed
- The sandbox environment appears unstable
Step-by-Step Instructions
Step 1: Preserve the Failed Code
When execute_code_sandbox fails, capture the Python code that was attempted. If the code was generated but not saved, reconstruct it from the execution attempt.
Step 2: Write Code to File
Use write_file to save the Python script to a .py file:
write_file with:
- path: "script_name.py" (e.g., "generate_report.py", "process_data.py")
- content: <the full Python code>
Example:
# Content for write_file
import pandas as pd
from openpyxl import Workbook
# Your spreadsheet generation logic here
df = pd.DataFrame({'Revenue': [100, 200, 300]})
df.to_excel('output.xlsx', index=False)
Step 3: Execute via run_shell
Run the saved script using run_shell with Python 3:
run_shell with:
- command: "python3 script_name.py"
- timeout: 60 (or higher for complex operations)
Step 4: Verify Output
Check that the expected output files were created:
list_dir with:
- path: "."
Or read the generated file to confirm correctness:
read_file with:
- file_path: "output.xlsx"
- filetype: "xlsx"
Complete Example
Scenario: Generate an Excel P&L report after sandbox failure.
# Step 1: Write the Python script
write_file:
path: "generate_pnl_report.py"
content: |
import pandas as pd
from openpyxl import Workbook
# Create revenue data
data = {
'Tour Stop': ['London', 'Paris', 'Berlin'],
'Revenue': [50000, 45000, 38000],
'Withholding Tax': [5000, 4500, 3800],
'Expenses': [12000, 11000, 9500]
}
df = pd.DataFrame(data)
df['Net Income'] = df['Revenue'] - df['Withholding Tax'] - df['Expenses']
# Export to Excel
df.to_excel('pnl_report.xlsx', index=False)
print("Report generated successfully")
# Step 2: Execute the script
run_shell:
command: "python3 generate_pnl_report.py"
timeout: 60
# Step 3: Verify
list_dir:
path: "."
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.
- 6d ago First seen · 133 lines · 23 tokens per session scan A 7cd4de6c07ff
sandbox-failure-recovery is a skill published in the GitHub repository HKUDS/OpenSpace (7,552 stars, last pushed 28d ago), licensed MIT. It adds 23 tokens to every session and 892 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…