菜单
Cowork mounts the plugin install dir under /sessions/CODENAME/mnt/.remote-plugins/ read-only. Bundled scripts can be launched via relative path; CLAUDE_SKILL_DIR expands to a Windows path that fails directly. CLI baseline lets both patterns work. See research section 2.10.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Mac Cowork で、plugin-level SessionStart hook(host 側)から $CLAUDE_PLUGIN_DATA に書いた値が「別の chat session を跨いで」残るかを検証する probe。書き込み＆読み戻しは hook(persist.sh)側で行い、その結果は SessionStart の stdout として context に出る。この skill body は対比用に「VM Bash 側から DATA が見えるか／hook が書いたファイルを読めるか」を確認する。
Surfaces UPE_PROBE_* marker lines to test whether the plugin-level UserPromptExpansion hook fires on Cowork. Invoking this skill via slash is itself the trigger; compares against UserPromptSubmit and SessionStart controls.
Triggers the plugin-level PreToolUse hooks by running a sentinel bash command, to test (via session export) whether Cowork runs PreToolUse hook commands through cmd.exe or a POSIX shell, and whether the inline block pattern actually blocks the bash tool.
Surfaces the EXEC_* marker lines emitted by the plugin-level SessionStart hooks, which run hook commands in EXEC FORM (args present). Used to test whether exec form resolves ${CLAUDE_PLUGIN_ROOT} to a real path and exports it as an env var on Cowork, where shell form (§2.1/§2.2) failed both.
Shows what skill-body CLAUDE_PLUGIN_ROOT and friends substitute to on Mac Cowork, whether the VM Bash tool can use that path, and whether the Read tool can read a bundled file at that host path.
Proves whether a skill frontmatter PreToolUse Bash hook fires on Cowork by emitting only a block decision (no echo). A marked bash should be blocked even though no frontmatter stdout surfaces.
| name | 17-cowork-bash-mount |
| description | Cowork mounts the plugin install dir under /sessions/CODENAME/mnt/.remote-plugins/ read-only. Bundled scripts can be launched via relative path; CLAUDE_SKILL_DIR expands to a Windows path that fails directly. CLI baseline lets both patterns work. See research section 2.10. |
| user-invocable | true |
§2.10 — bundled script の起動パターン 2 種 + 罠（mkdir -p ゴミ、tee silent fail）。
proj="${CLAUDE_PROJECT_DIR:-$PWD}"
ver="${VERIFIER_VERSION_DIR:-v-unknown}"
sid="${CLAUDE_SESSION_ID:-no-sid}"
out_dir="$proj/findings/$ver/$sid"
mkdir -p "$out_dir"
{
printf '[17-BODY %s] tag=alive-check\n' "$(date -Iseconds)"
printf '[17-BODY] CLAUDE_SKILL_DIR=[%s]\n' "${CLAUDE_SKILL_DIR-(unset)}"
printf '[17-BODY] CLAUDE_PLUGIN_ROOT=[%s]\n' "${CLAUDE_PLUGIN_ROOT-(unset)}"
} | tee -a "$out_dir/probe.log"
# Pattern A: find then cd
skill_dir=$(find /sessions -path '*/skills/17-cowork-bash-mount' -type d 2>/dev/null | head -1)
if [ -z "$skill_dir" ]; then
# CLI: SKILL_DIR is a Linux path so use it directly
skill_dir="${CLAUDE_SKILL_DIR}"
fi
echo "Pattern A: cd $skill_dir && bash scripts/say-hi.sh" | tee -a "$out_dir/probe.log"
( cd "$skill_dir" 2>/dev/null && bash scripts/say-hi.sh ) 2>&1 | tee -a "$out_dir/probe.log"
proj="${CLAUDE_PROJECT_DIR:-$PWD}"
ver="${VERIFIER_VERSION_DIR:-v-unknown}"
sid="${CLAUDE_SESSION_ID:-no-sid}"
out_dir="$proj/findings/$ver/$sid"
echo "Pattern B: bash \"${CLAUDE_SKILL_DIR}/scripts/say-hi.sh\"" | tee -a "$out_dir/probe.log"
bash "${CLAUDE_SKILL_DIR}/scripts/say-hi.sh" 2>&1 | tee -a "$out_dir/probe.log" || echo "[17-PATTERN-B exited non-zero (expected on Cowork)]" | tee -a "$out_dir/probe.log"
proj="${CLAUDE_PROJECT_DIR:-$PWD}"
ver="${VERIFIER_VERSION_DIR:-v-unknown}"
sid="${CLAUDE_SESSION_ID:-no-sid}"
out_dir="$proj/findings/$ver/$sid"
before_pwd_listing=$(ls "$PWD" 2>/dev/null | head -20)
mkdir -p "${CLAUDE_PLUGIN_DATA}" 2>&1
after_pwd_listing=$(ls "$PWD" 2>/dev/null | head -20)
{
printf '[17-BODY trap-mkdir] before=%s\n' "$(echo $before_pwd_listing | tr '\n' ' ' | head -c 200)"
printf '[17-BODY trap-mkdir] after=%s\n' "$(echo $after_pwd_listing | tr '\n' ' ' | head -c 200)"
} | tee -a "$out_dir/probe.log"
完了して exit、./scripts/assert.sh 17。