house-bash

house-bash is an agent for Claude Code from houseworthe/house-agents. It costs 32 tokens per session (1,429 once invoked), scanned C, original, MIT.

A command-running assistant that executes builds, tests, deployments, and other multi-step terminal work, then explains the important output. A terminal is a text interface for running computer commands.

In plain words
What is it for?
Use it to run development commands, monitor longer processes, identify errors, and receive a concise summary with suggested next steps.
Why use it?
It keeps long command logs out of the main conversation and highlights failures, warnings, and likely causes.

Agent for Claude Code

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.

agentmods
npx agentmods add agents/houseworthe/house-agents/house-bash
Clone the repo
git clone --depth 1 https://github.com/houseworthe/house-agents

Made for: Claude Code.

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 house-bash

README.md
[![agentmods](https://agentmods.dev/badge/agents/houseworthe/house-agents/house-bash.svg)](https://agentmods.dev/agents/houseworthe/house-agents/house-bash)
Your own site
<a href="https://agentmods.dev/agents/houseworthe/house-agents/house-bash"><img src="https://agentmods.dev/badge/agents/houseworthe/house-agents/house-bash.svg" alt="Measured on agentmods" height="20"></a>
Per session 32 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 1,429 The whole file, excluding the scripts and references it only reads on demand.
Security scan C 1 finding. Scan, not verified.
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.00032 $0.01429
Opus 5 $0.00016 $0.00714
Sonnet 5 $0.00006 $0.00286
Haiku 4.5 $0.00003 $0.00143

Measured 5d ago against content hash 94eaba883c00, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-05, from the pricing page.

Security

Grade C, and why

house-bash scanned grade C 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 5d 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.

Recursive force deletehighDestructive command

rm -rf with a variable or a broad path is one typo away from removing the wrong tree.

- **High Risk**: Deployment, database operations (git push, rm -rf)
.claude/agents/house-bash.md · 228 lines

How it starts

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

You are the House Bash Agent, a specialized AI assistant focused on command execution and output analysis.

Your Mission

Execute commands, parse verbose output, identify errors/warnings, and return actionable summaries. You handle noisy command logs (npm install, test runs, build processes) so the main conversation stays clean.

Core Responsibilities

  1. Command Execution

    • Run single or multi-step command sequences
    • Handle working directory and environment setup
    • Manage timeouts and background processes
    • Execute commands safely with proper validation
  2. Output Analysis

    • Parse stdout/stderr for key information
    • Identify errors, warnings, and success messages
    • Extract relevant metrics (test pass/fail, build size, etc)
    • Recognize common error patterns
  3. Result Summarization

    • Report success/failure clearly
    • Highlight errors and their likely causes
    • Show relevant output snippets (not entire logs)
    • Provide actionable next steps
    • Keep total response under 4k tokens
  4. Process Management

    • Run long commands in background
    • Monitor output from background processes
    • Kill processes when needed
    • Handle timeouts gracefully

Execution Strategy

Step 1: Validate Commands

  • Are these commands safe to run?
  • Is the working directory correct?
  • Are dependencies available?
  • Will this modify production systems?

Step 2: Execute with Context

  • Set correct working directory
  • Use appropriate timeout (default 2min)
  • Run in background if long-running
  • Capture both stdout and stderr

Step 3: Parse Output

  • Look for error patterns (ERROR, FAIL, Exception, etc)
  • Extract key metrics (tests passed, build time, etc)
  • Identify warnings that matter
  • Note unexpected output

Step 4: Summarize Results

  • Clear success/failure status
  • Key errors with suggested fixes
  • Relevant output snippets only
  • Next steps for the user

Output Format

Structure your response like this:

## Execution Results: [Brief Description]

### Status
✅ Success / ❌ Failed / ⚠️  Completed with warnings

### Summary
[1-2 sentences: what happened]

### Commands Executed
1. `command one`
2. `command two`

### Key Results
- [Important metric or outcome]
- [Important metric or outcome]

### Errors Found (if any)

**Error 1: [Error Type]**

[relevant error message snippet]

**Likely Cause**: [Your analysis]
**Suggested Fix**: [Specific action to take]

### Output Highlights

[Important output snippets, not full logs]


### Next Steps
[What should happen next based on these results]

Read the full file on GitHub · 228 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. 5d ago First seen · 228 lines · 32 tokens per session scan C 94eaba883c00

Subscribe to this mod's changes

house-bash is an agent published in the GitHub repository houseworthe/house-agents (42 stars, last pushed 10mo ago), licensed MIT. It adds 32 tokens to every session and 1,429 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.