bash-timeout

bash-timeout is a command for Claude Code from GoogilyBoogily/googilyboogily-claude-power-tools. It costs 8 tokens per session (836 once invoked), scanned B, original, MIT.

A command for changing Bash timeout settings in Claude Code’s settings.json file. Bash is the shell used to run commands such as builds and tests.

In plain words
What is it for?
Setting default and maximum time limits for builds, tests, deployments, and other Bash commands.
Why use it?
It helps prevent long-running commands from stopping at the default two-minute limit.

Command for Claude Code

Written for Claude Code: allowed-tools in frontmatter. Also seen: reads .claude/ paths; mentions Claude Code.

Part of the dev-utilities plugin — 2 commands shipped together

Good fit Setting default and maximum time limits for builds, tests, deployments, and other Bash commands.

Compare 6 commands from other repositories ↓
Install with agentmods
npx agentmods add commands/googilyboogily/googilyboogily-claude-power-tools/bash-timeout
Install

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.

Clone the repo
git clone --depth 1 https://github.com/GoogilyBoogily/googilyboogily-claude-power-tools

Made for: Claude Code.

Or install dev-utilities, the plugin that ships this one along with the rest of its 2 commands.

Wrote 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.

agentmods badge for bash-timeout

README.md
[![agentmods](https://agentmods.dev/badge/commands/googilyboogily/googilyboogily-claude-power-tools/bash-timeout/github.svg)](https://agentmods.dev/commands/googilyboogily/googilyboogily-claude-power-tools/bash-timeout)
Your own site
<a href="https://agentmods.dev/commands/googilyboogily/googilyboogily-claude-power-tools/bash-timeout"><img src="https://agentmods.dev/badge/commands/googilyboogily/googilyboogily-claude-power-tools/bash-timeout/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.

agentmods 80×15 button for bash-timeout

Your own site · 80×15
<a href="https://agentmods.dev/commands/googilyboogily/googilyboogily-claude-power-tools/bash-timeout"><img src="https://agentmods.dev/badge/commands/googilyboogily/googilyboogily-claude-power-tools/bash-timeout.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 8 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 836 The whole file, excluding the scripts and references it only reads on demand.
Security scan B 1 finding. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00008 $0.00836
Opus 5 $0.00004 $0.00418
Sonnet 5 $0.00002 $0.00167
Haiku 4.5 $0.00001 $0.00084

Measured 11d ago against content hash 0f8cec753c18, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade B, and why

bash-timeout 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 11d 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.

User settings: !if [ -f ~/.claude/settings.json ]; then if command -v jq &>/dev/null; then cat ~/.claude/settings.json | jq '.env // {}' 2>/dev/null; else cat ~/.claude/settings.json | grep -A 10 '"env"' 2>/dev/null || e
plugins/dev-utilities/commands/bash-timeout.md · 87 lines

How it starts

The opening of the file, as written. The whole thing — 87 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Configure Bash Timeout Settings

Configure the bash command timeout values in your Claude Code settings.json file. The default timeout is 2 minutes (120000ms), which is often insufficient for long-running operations like builds, tests, or deployments.

Current Settings

User settings: !if [ -f ~/.claude/settings.json ]; then if command -v jq &>/dev/null; then cat ~/.claude/settings.json | jq '.env // {}' 2>/dev/null; else cat ~/.claude/settings.json | grep -A 10 '"env"' 2>/dev/null || echo "No env settings found"; fi; else echo "No user settings file"; fi Project settings: !if [ -f .claude/settings.json ]; then if command -v jq &>/dev/null; then cat .claude/settings.json | jq '.env // {}' 2>/dev/null; else cat .claude/settings.json | grep -A 10 '"env"' 2>/dev/null || echo "No env settings found"; fi; else echo "No project settings file"; fi

Available Timeout Settings

  • BASH_DEFAULT_TIMEOUT_MS: The default timeout for bash commands (in milliseconds)
  • BASH_MAX_TIMEOUT_MS: The maximum timeout that can be set for bash commands (in milliseconds)

Common Timeout Values

  • 2 minutes: 120000 (default)
  • 5 minutes: 300000
  • 10 minutes: 600000
  • 15 minutes: 900000
  • 20 minutes: 1200000
  • 30 minutes: 1800000

Configure Settings

  1. First, check if settings.json exists in the appropriate location
  2. Read the current settings to preserve existing configuration
  3. Add or update the env section with the desired timeout values
  4. Maintain all existing settings (hooks, etc.)

For User-Level Settings (~/.claude/settings.json)

  • Applies to all projects for the current user
  • Location: ~/.claude/settings.json

For Project-Level Settings (.claude/settings.json)

  • Applies only to the current project
  • Location: .claude/settings.json
  • Project settings override user settings

Arguments

Specify the timeout duration (e.g., "10min", "20min", "5m", "600s") and optionally the scope:

  • $ARGUMENTS format: [duration] [scope]
  • Duration: Required (e.g., "10min", "20min", "300s")
  • Scope: Optional - "user" (default) or "project"

Read the full file on GitHub · 87 lines

Changes

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.

  1. 11d ago First seen · 87 lines · 8 tokens per session scan B 0f8cec753c18

Subscribe to this mod's changes

bash-timeout is a command published in the GitHub repository GoogilyBoogily/googilyboogily-claude-power-tools (2 stars, last pushed 3mo ago), licensed MIT. It adds 8 tokens to every session and 836 once invoked, about $0.0000 per session on Opus 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-31.