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-root-directorygit 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-root-directory)<a href="https://agentmods.dev/skills/eaglesakura/agent-skills/workspace-resolve-root-directory"><img src="https://agentmods.dev/badge/skills/eaglesakura/agent-skills/workspace-resolve-root-directory/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-root-directory"><img src="https://agentmods.dev/badge/skills/eaglesakura/agent-skills/workspace-resolve-root-directory.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.00376 | $0.05973 |
| Opus 5 | $0.00188 | $0.02986 |
| Sonnet 5 | $0.00075 | $0.01195 |
| Haiku 4.5 | $0.00038 | $0.00597 |
Grade A, and why
workspace-resolve-root-directory 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 — 341 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workspace / Resolve Root Directory
VS Code / Cursor の Workspace では、ルートに表示名が付くことがある。
参照は次の 系統で書く。ドキュメント・プロンプトでは @{name} を優先し、
folder:{name} は同じ意味の互換記法としてどちらもパースする（Cursor の @ 参照と揃える）。
| 記法 | ルートの意味（Multi-Root） | ルートの意味（単一ルート） |
|---|---|---|
@{name}/...（優先） |
folders[].name → folders[].path（エディタ上のルート） |
{name} を無視し、開いているワークスペースディレクトリ |
folder:{name}/...（互換） |
上と同一（@{name}/... と同じ FOLDER_ROOT） |
上と同一 |
repo:{name}/... |
その folder 起点の Git リポジトリルート | {name} を無視し、開いているワークスペース起点の Git ルート |
@example/... / folder:example/... / repo:example/... |
変数。文脈から実 folders[].name へ読み替えてから上記どおり解決 |
{name} 無視（単一ルート互換。読み替え不要） |
@this/... / folder:this/... / 指定なし |
表記元が属する workspace folder（最長一致） | 開いているワークスペースディレクトリ |
repo:this/... |
表記元が属する Git リポジトリルート | 同左 |
等価の例: folder:HQ と @HQ は同じディレクトリ（name == "HQ" の folders[].path）を指す。
repo:HQ は Git ルート側であり、@HQ / folder:HQ とは一致しないことがある。
Multi-Root では通常の {name} は ディレクトリ名ではなく folders[].name を使う（パス断片の推測はしない）。
例外として予約変数 example だけは、プロンプト／タスク文脈に応じて実 name へ読み替えてよい（下記 特殊ルール / example）。
folders[].path がリポジトリのサブディレクトリを指すと、@ / folder: と repo: は一致しない。
例: name=docs の path が docs-workspace/ でも、Git ルートが親の example-monorepo/ なら、@docs/README.md（=folder:docs/README.md）と repo:docs/README.md は別ファイルになる。
いつ使うか
- 表記が
@{name}/...・folder:{name}/...・repo:{name}/...のとき（Multi-Root / 単一ルートどちらでも） @example/.../folder:example/.../repo:example/...を文脈の対象ルートへ読み替えるとき- ルート名の指定が無く、workspace folder 相対として解く必要があるとき（暗黙の
@this/=folder:this/） - 「
@docs/.../folder:docs/.../repo:docs/.../@thisの実体は？」「folders 名で解決して」と聞かれたとき
いつ使わないか
- クォート相対
path/to/file（Git リポジトリルート相対が意図）・Markdown リンク →workspace-resolve-file-path .ai-agent/の導入・置き場 →workspace-layout/workspace-agent-temporary{assets}/...または@/folder:/repo:付き{assets}/...→workspace-resolve-agent-assets（スコープは本 SKILL の規則で決める）- URL → タスクID / タイトル（本 SKILL の範囲外）
- チャット上のメンション（例: ユーザー
@eaglesakura）や、workspace folder 名ではない単なる@記号 → 本 SKILL のパス解決対象外
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.
- 9d ago First seen · 341 lines · 376 tokens per session scan A 3664a4e73d7c
workspace-resolve-root-directory is a skill published in the GitHub repository eaglesakura/agent-skills (2 stars, last pushed 3d ago), licensed MIT. It adds 376 tokens to every session and 5,973 once invoked, about $0.0019 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…