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 nebius/nebius-physical-ai --skill find-artifactsgit clone --depth 1 https://github.com/nebius/nebius-physical-aiWrote 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/nebius/nebius-physical-ai/find-artifacts)<a href="https://agentmods.dev/skills/nebius/nebius-physical-ai/find-artifacts"><img src="https://agentmods.dev/badge/skills/nebius/nebius-physical-ai/find-artifacts/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/nebius/nebius-physical-ai/find-artifacts"><img src="https://agentmods.dev/badge/skills/nebius/nebius-physical-ai/find-artifacts.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.00022 | $0.00635 |
| Opus 5 | $0.00011 | $0.00318 |
| Sonnet 5 | $0.00004 | $0.00127 |
| Haiku 4.5 | $0.00002 | $0.00064 |
Grade A, and why
find-artifacts 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 9d 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 — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Find Artifacts (artifact-first)
Use this skill when the operator asks:
- "what can I view?"
- "show artifacts for this run"
- "load this recording/video/report"
- "browse outputs from storage"
Model
Artifact-first means:
- Enumerate what exists in storage.
- Group by discovered run prefix.
- Classify each object with a render hint.
- Never hide unknown formats; degrade to download.
No workflow registry, path allowlist, or known-type gate is required.
Agent API flow
All calls are same-origin (/api/...) on the authenticated agent VM.
- Discover runs:
GET /api/artifacts/runs?prefix=&limit=100
- List artifacts for one run:
GET /api/artifacts/run/{run_id}
- Load one explicit artifact:
POST /api/sim-viz/load-artifact
{
"run_id": "run-prefix",
"run_ref": "<server-issued opaque run reference>",
"project_id": "<selected project>",
"resource_bucket": "<selected bucket>",
"resolved_prefix": "<selected prefix, possibly empty>",
"source_selected": true,
"key": "path/to/run/object"
}
Preserve this exact source tuple from list response to card, thumbnail, preview,
download, and load action. s3_uri is provenance only: URI-only or otherwise
unscoped media requests are rejected with a stable 400 response because bucket
membership alone is not run-level authorization. Follow every artifact-page
cursor before computing preference; the shipped UI does this automatically.
- Confirm loaded state:
GET /api/sim-viz/status
Check artifact_key, artifact_render, artifact_uri, and rerun_ready.
Render hints
rerun(.rrd)video(.mp4,.webm,.mov)image(.png,.jpg,.jpeg,.gif,.webp)jsontextdownload(fallback for unknown/new types)
Unknown types must stay visible/selectable.
Safety
- Validate run ids (
validate_run_id) before listing/loading. - Reject traversal keys (
.., empty segments). - Surface S3 failures directly (
ok: falseor error detail); do not claim success when load/list fails. - Agent artifact discovery is S3-first and S3-only for run artifacts. The agent
must stage the configured artifact bucket credentials, upload completed run
artifacts there, and use
/api/artifacts/runs,/api/artifacts/run/{run_id}, and/api/sim-viz/load-artifactagainst that S3 data. Do not silently fall back to/opt/npa-agent/runsfor user-visible discovery.
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.
- 9d ago First seen · 93 lines · 22 tokens per session scan A 0cdc818da4cf
find-artifacts is a skill published in the GitHub repository nebius/nebius-physical-ai (27 stars, last pushed today), licensed Apache-2.0. It adds 22 tokens to every session and 635 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-08-30.
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…