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 eaglesakura/agent-skills --skill workspace-resolve-agent-assetsgit clone --depth 1 https://github.com/eaglesakura/agent-skillsWrote 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/eaglesakura/agent-skills/workspace-resolve-agent-assets)<a href="https://agentmods.dev/skills/eaglesakura/agent-skills/workspace-resolve-agent-assets"><img src="https://agentmods.dev/badge/skills/eaglesakura/agent-skills/workspace-resolve-agent-assets/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/eaglesakura/agent-skills/workspace-resolve-agent-assets"><img src="https://agentmods.dev/badge/skills/eaglesakura/agent-skills/workspace-resolve-agent-assets.svg" alt="Reviewed on agentmods" width="80" 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.00266 | $0.04132 |
| Opus 5 | $0.00133 | $0.02066 |
| Sonnet 5 | $0.00053 | $0.00826 |
| Haiku 4.5 | $0.00027 | $0.00413 |
Grade A, and why
workspace-resolve-agent-assets 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 10d 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 — 258 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workspace / Resolve Agent Assets
APM などでインストール先が変わっても参照を保てるよう、アセットは メタ変数 {assets}/ で書く。
本 SKILL はその表記を、文書に書かれた候補ディレクトリから実パスへ落とす。
探索の スコープルート は、暗黙ではインストール先ワークスペース（@this）、明示では @app/ 等で切り替える（解決は workspace-resolve-root-directory に従う）。
apm install・fork・_local 展開などで apm_modules/ 配下が揺れる場合は、候補にワイルドカードを書いて複数レイアウトを一度に拾う。
いつ使うか
- コマンド / SKILL 本文や関連ファイルに
{assets}/template.mdのように書かれているとき @app/{assets}/.../repo:backend/{assets}/.../@this/{assets}/...のようにルート付きでアセットを指すとき- パッケージソースと
apm_modules/展開先の両方に同じアセットがあり得るとき - 「アセットを解決してから読んで」「
{assets}/の実体はどこ？」と聞かれたとき
いつ使わないか
- クォート相対
path/to/file、Markdown リンク[text](rel)→workspace-resolve-file-path {assets}/を含まない純粋な@/repo:パスだけ →workspace-resolve-root-directory.ai-agent/の導入・置き場 →workspace-layout/workspace-agent-temporary- GitHub Issue URL から ID/タイトルを取る（本 SKILL の範囲外）
- キーワードで文書を探すだけ →
markdown-search
作業手順
- 参照文字列に
@/repo:があれば剥がし、スコープルートを決める（下記） {assets}/以降をサフィックスとする- 基準ファイルから候補ディレクトリ一覧を集める（候補行自体に
@/repo:があれば、行ごとにスコープを上書きしてよい） - 各候補について、リテラルならそのまま・ワイルドカードなら展開し、文書相対と スコープルート相対（必要ならその Git ルート相対）で存在確認する
- ヒットを明示し、1 件なら採用、0 件なら推測読みしない
スコープルート（@ / repo: / 暗黙の @this）
アセット探索の「ルート相対」ベースを決める。詳細アルゴリズムは workspace-resolve-root-directory に従う。
| 指定 | 意味 |
|---|---|
無し（通常の {assets}/...） |
暗黙の @this — 基準ファイルが属する インストール先ワークスペース folder |
@this/... |
同上を明示 |
@{name}/...（例: @app/） |
その Multi-Root folder（または単一ルート互換）をスコープにする。プロジェクト専用 SKILL から他ルートのアセットを指すときに使う |
repo:{name}/... / repo:this/... |
対応する Git リポジトリルートをスコープにする |
参照例:
{assets}/template.md→ スコープ =@this、サフィックス =template.md@app/{assets}/example-skill/assets→ スコープ =@app、サフィックス =example-skill/assetsrepo:backend/{assets}/template.md→ スコープ =repo:backend、サフィックス =template.md
@example / repo:example の文脈読み替えも root-directory の変数規則に従う。
スコープが決まらない（name 不一致・文脈不足）ときはアセット探索に進まず、root-directory と同様に候補 name を報告する。
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.
- 10d ago First seen · 258 lines · 266 tokens per session scan A b201fe913abe
workspace-resolve-agent-assets is a skill published in the GitHub repository eaglesakura/agent-skills (2 stars, last pushed 5d ago), licensed MIT. It adds 266 tokens to every session and 4,132 once invoked, about $0.0013 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-31.
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…