ワンクリックでManusで任意のスキルを実行

04-sensitive-leak

スター0

フォーク0

更新日2026年5月21日 04:34

Confirm that userConfig.api_secret (sensitive=true) is exposed as plain text via CLAUDE_PLUGIN_OPTION_API_SECRET in plugin-level hook env (§1.4). "sensitive" affects storage only, not runtime exposure.

インストール

Codex または Claude でインストールこの Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。

Manusで実行

ソース

kazukinagata

kazukinagata/analyzing-claude-plugin

GitHub リポジトリを開く Creator のリポジトリを見る

ダウンロード

Manusで実行

04-sensitive-leak

§1.4 — sensitive: true は保存先（keychain）の分離のみで、ランタイムでは平文で env に渡る。

事前準備：findings/claude-home/settings.json または ~/.claude/.credentials.json に以下を設定済みであること：

hello_message = hello-from-cli-CANARY
api_secret = secret-xyz-CANARY

step 1: alive-check と hooks.log の env を確認

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 '[04-BODY %s] tag=alive-check\n' "$(date -Iseconds)"
  printf '[04-BODY] CLAUDE_PLUGIN_OPTION_HELLO_MESSAGE=[%s]\n' "${CLAUDE_PLUGIN_OPTION_HELLO_MESSAGE-(unset)}"
  printf '[04-BODY] CLAUDE_PLUGIN_OPTION_API_SECRET=[%s]\n' "${CLAUDE_PLUGIN_OPTION_API_SECRET-(unset)}"
} | tee -a "$out_dir/probe.log"
echo
echo "=== hooks.log (plugin-level env) ==="
grep -E "OPTION_HELLO|OPTION_API_SECRET|substituted" "$out_dir/hooks.log" 2>&1 || echo "(no match)"
echo
echo "=== settings.json (pluginConfigs) ==="
cat "$CLAUDE_CONFIG_DIR/settings.json" 2>&1 || echo "(no settings.json)"
echo
echo "=== .credentials.json (if present, contents redacted) ==="
[ -f "$CLAUDE_CONFIG_DIR/.credentials.json" ] && echo "exists at $CLAUDE_CONFIG_DIR/.credentials.json" || echo "(none)"

完了して exit、./scripts/assert.sh 04。

このリポジトリの他の Skills

同じリポジトリ

data-persist

kazukinagata/analyzing-claude-plugin

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 が書いたファイルを読めるか」を確認する。

2026-06-010

show-upe

kazukinagata/analyzing-claude-plugin

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.

2026-05-300

run-pretooluse-probe

kazukinagata/analyzing-claude-plugin

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.

2026-05-300

show-exec-form

kazukinagata/analyzing-claude-plugin

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.

2026-05-290

bodypath

kazukinagata/analyzing-claude-plugin

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.

2026-05-290

fm-bashblock

kazukinagata/analyzing-claude-plugin

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.

2026-05-290

name	04-sensitive-leak
description	Confirm that userConfig.api_secret (sensitive=true) is exposed as plain text via CLAUDE_PLUGIN_OPTION_API_SECRET in plugin-level hook env (§1.4). "sensitive" affects storage only, not runtime exposure.
user-invocable	true

04-sensitive-leak

§1.4 — sensitive: true は保存先（keychain）の分離のみで、ランタイムでは平文で env に渡る。

事前準備：findings/claude-home/settings.json または ~/.claude/.credentials.json に以下を設定済みであること：

hello_message = hello-from-cli-CANARY
api_secret = secret-xyz-CANARY

step 1: alive-check と hooks.log の env を確認

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 '[04-BODY %s] tag=alive-check\n' "$(date -Iseconds)"
  printf '[04-BODY] CLAUDE_PLUGIN_OPTION_HELLO_MESSAGE=[%s]\n' "${CLAUDE_PLUGIN_OPTION_HELLO_MESSAGE-(unset)}"
  printf '[04-BODY] CLAUDE_PLUGIN_OPTION_API_SECRET=[%s]\n' "${CLAUDE_PLUGIN_OPTION_API_SECRET-(unset)}"
} | tee -a "$out_dir/probe.log"
echo
echo "=== hooks.log (plugin-level env) ==="
grep -E "OPTION_HELLO|OPTION_API_SECRET|substituted" "$out_dir/hooks.log" 2>&1 || echo "(no match)"
echo
echo "=== settings.json (pluginConfigs) ==="
cat "$CLAUDE_CONFIG_DIR/settings.json" 2>&1 || echo "(no settings.json)"
echo
echo "=== .credentials.json (if present, contents redacted) ==="
[ -f "$CLAUDE_CONFIG_DIR/.credentials.json" ] && echo "exists at $CLAUDE_CONFIG_DIR/.credentials.json" || echo "(none)"

完了して exit、./scripts/assert.sh 04。