locate-missing-artifacts

locate-missing-artifacts is a skill for Claude Code, Codex from HKUDS/OpenSpace. It costs 24 tokens per session (1,012 once invoked), scanned C, original, MIT.

A recovery guide for finding generated files that are missing from their expected location in a restricted or temporary environment.

In plain words
What is it for?
Use it to locate generated artifacts, investigate path mismatches, and copy recovered files to the locations where later steps expect them.
Why use it?
It provides a structured way to confirm a file is missing, identify trusted folders, and search for the file when a tool reported success but the output cannot be found.

Skill for Claude CodeCodex

Install

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.

agentmods
npx agentmods add skills/hkuds/openspace/locate-missing-artifacts
Any agent
npx skills add HKUDS/OpenSpace --skill locate-missing-artifacts
Clone the repo
git clone --depth 1 https://github.com/HKUDS/OpenSpace

Made for: Claude Code, Codex.

Wrote 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.

agentmods badge for locate-missing-artifacts

README.md
[![agentmods](https://agentmods.dev/badge/skills/hkuds/openspace/locate-missing-artifacts.svg)](https://agentmods.dev/skills/hkuds/openspace/locate-missing-artifacts)
Your own site
<a href="https://agentmods.dev/skills/hkuds/openspace/locate-missing-artifacts"><img src="https://agentmods.dev/badge/skills/hkuds/openspace/locate-missing-artifacts.svg" alt="Measured on agentmods" height="20"></a>
Per session 24 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,012 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00024 $0.01012
Opus 5 $0.00012 $0.00506
Sonnet 5 $0.00005 $0.00202
Haiku 4.5 $0.00002 $0.00101

Measured 4d ago against content hash 49610de42e72, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade C, and why

locate-missing-artifacts scanned grade C with 1 finding 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.

Enumerates the file system for secretshighData exfiltration

Searching home directories for .env, .ssh, .aws or credential files is reconnaissance for credential theft.

ls -la $HOME ls -la /tmp
benchmarks/gdpval/skills/locate-missing-artifacts/SKILL.md · 146 lines

How it starts

The opening of the file, as written. The whole thing — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Locate Missing Artifacts in Sandboxed Environments

When to Use This Skill

Use this skill when:

  • A tool reports success but files are not found in their expected locations
  • You receive errors like "file not found" after a tool claims to have created it
  • You're working in a sandboxed/ephemeral environment where file paths may shift
  • Directory structure mismatches occur between tool execution and validation

Step-by-Step Instructions

Step 1: Confirm the Failure

Before searching, verify the file is actually missing from the expected location:

ls -la /expected/path/filename.ext
# or
test -f /expected/path/filename.ext && echo "Found" || echo "Missing"

Step 2: Identify Confirmed Root Directories

Determine which directories you know exist and where tools typically write:

# Common roots to check
ls -la /
ls -la $HOME
ls -la /tmp
ls -la /workspace
ls -la .

Step 3: Search for the Artifact Using find

Use find from confirmed root directories to locate the missing file:

# Search by filename
find /workspace -name "filename.ext" 2>/dev/null

# Search by pattern if exact name varies
find /workspace -name "*.ext" 2>/dev/null

# Search broader paths if needed
find / -name "filename.ext" 2>/dev/null | head -20

Step 4: Copy Artifact to Expected Location

Once located, explicitly copy the file to where it should be:

# Copy to expected location
cp /found/path/filename.ext /expected/path/filename.ext

# Or if you need to preserve the original
cp -r /found/path/filename.ext /expected/path/

# Verify the copy succeeded
ls -la /expected/path/filename.ext

Step 5: Validate Before Proceeding

Confirm the file is now accessible at the expected location:

# Test file exists and is readable
test -f /expected/path/filename.ext && test -r /expected/path/filename.ext && echo "Ready"

# Check file size to ensure it's not empty
stat /expected/path/filename.ext

Common Patterns

Pattern: Output Written to Wrong Directory

Read the full file on GitHub · 146 lines

Files

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.

Changes

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.

  1. 4d ago First seen · 146 lines · 24 tokens per session scan C 49610de42e72

Subscribe to this mod's changes

locate-missing-artifacts is a skill published in the GitHub repository HKUDS/OpenSpace (7,501 stars, last pushed 22d ago), licensed MIT. It adds 24 tokens to every session and 1,012 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it C with 1 finding (enumerates the file system for secrets). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

obra/superpowers · 37 tokens

auto-perf-optimize

Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.

microsoft/vscode · 62 tokens

chat-perf

Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.

microsoft/vscode · 51 tokens

chat-pet-sprite-creation

Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.

microsoft/vscode · 53 tokens

cpu-profile-analysis

Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…

microsoft/vscode · 71 tokens