メニュー
Use when deciding whether shell commands are truly read-only, safe for concurrent execution, and free of path, git, redirection, or command-shape risks that should force a stricter permission path
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when verifying implementation work and the failure mode is superficial approval, code-reading in place of execution, or over-trusting a passing test suite without trying to break the change
Use when coordinating multi-step work across workers or subagents, especially when research, implementation, and verification should be split while the main agent stays responsible for synthesis and user communication
Use when the task is codebase exploration rather than modification, and you need a fast, read-only search pattern that starts broad when location is unknown, narrows when location is known, and parallelizes independent searches
Use when deciding what information belongs in memory, how to classify it, and what must not be saved because it is derivable from the repo, git history, or current task context
Use when the real risk is not lack of knowledge but self-justifying shortcuts such as explaining instead of running commands, skipping the hard part first, or deciding on your own that verification would take too long
Use when maintaining session notes that must preserve a fixed markdown template, stay within section and total token budgets, and remain useful after compaction or resume
| name | read-only-shell-guard |
| description | Use when deciding whether shell commands are truly read-only, safe for concurrent execution, and free of path, git, redirection, or command-shape risks that should force a stricter permission path |
Not every harmless-looking command is actually read-only. This skill follows the guardrails in src/tools/BashTool/readOnlyValidation.ts and related shell validation utilities.
A read-only command may inspect state, but it must not:
Usually safe when validated:
rg, grep, find, cat, head, tail, wc, statgit queriesgh queriesTreat the command as non-read-only when you see:
cd and git compound commands in sandboxed contextsThe whole command is only read-only if every subcommand is read-only.
One unsafe segment makes the batch unsafe.
Do not trust the command's story. Validate:
If validation fails or is ambiguous, escalate to stricter permission handling.
Read-only work may be run concurrently. Mixed or write-capable work must not inherit that privilege just because part of it looks harmless.
git is always read-onlyYou have applied this skill correctly when only truly read-only commands get the fast path, and ambiguous or risky command shapes are forced into the stricter permission path.