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 drn/dots --skill bash-tool-pathgit clone --depth 1 https://github.com/drn/dotsWrote 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/drn/dots/bash-tool-path)<a href="https://agentmods.dev/skills/drn/dots/bash-tool-path"><img src="https://agentmods.dev/badge/skills/drn/dots/bash-tool-path/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/drn/dots/bash-tool-path"><img src="https://agentmods.dev/badge/skills/drn/dots/bash-tool-path.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.00104 | $0.01140 |
| Opus 5.5 | $0.00042 | $0.00456 |
| Sonnet 5.5 | $0.00021 | $0.00228 |
| Haiku 4.5 | $0.00010 | $0.00114 |
Grade B, and why
bash-tool-path scanned grade B with 1 finding 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 1mo 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
- Existing SessionStart hooks (user): !`grep -n SessionStart ~/.claude/settings.json 2>/dev/null | head -10` How it starts
The opening of the file, as written. The whole thing — 93 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Context
- Worked example hook: ~/.dots/agents/hooks/session-start-path.sh
- Existing SessionStart hooks (user): !
grep -n SessionStart ~/.claude/settings.json 2>/dev/null | head -10 - env.PATH in user settings (a footgun if present): !
grep -n '"PATH"' ~/.claude/settings.json 2>/dev/null | head -5
When to use this skill
Use this when a command that works in an interactive terminal fails with "command not found" inside Claude Code's Bash tool, or when the user wants to add a directory (a go/bin, cargo, asdf shim, or custom tool dir) to the PATH that Claude Code's Bash tool sees.
Why the obvious fixes do not work
Three footguns make this harder than it looks. State them plainly so nobody re-discovers them by hand.
-
settings.json
envvalues are set literally. Claude Code does not expand$VARor${VAR}in them. So"PATH": "${PATH}:/x/bin"sets PATH to that literal, broken string, not to the inherited PATH plus a directory. -
env.PATHreplaces the inherited PATH wholesale. It cannot append, and replacing it drops the directories Claude Code already needs (for example plugin bin dirs). Soenv.PATHis the wrong tool for adding a dir. -
The Bash tool sources
~/.zshrc(or~/.bashrc/~/.profile) at session start only to capture aliases, functions, and shell options. PATHexportlines in~/.zshrcor~/.zshenvare not captured. Claude Code builds the Bash tool PATH from the process that launched it (often a daemon), not from your interactive shell, so daemon-launched sessions can lack go/bin and similar dirs even though they resolve fine in your terminal.
The supported fix: a SessionStart hook that writes to CLAUDE_ENV_FILE
Claude Code sources the file named by $CLAUDE_ENV_FILE before every Bash
command. Because the file is sourced, $PATH expands at source time, so you
can prepend a directory and preserve the inherited PATH. Populate that file
from a SessionStart hook. $CLAUDE_ENV_FILE is available to the
SessionStart, Setup, CwdChanged, and FileChanged hooks.
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.
- 1mo ago First seen · 93 lines · 104 tokens per session scan B 5281971a933c
bash-tool-path is a skill published in the GitHub repository drn/dots (23 stars, last pushed 11d ago), licensed MIT. It adds 104 tokens to every session and 1,140 once invoked, about $0.0004 per session on Opus 5.5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…