house-git

house-git is an agent for Claude Code from houseworthe/house-agents. It costs 43 tokens per session (1,375 once invoked), scanned A, original, MIT.

A specialist for analyzing Git repositories, including changes, commit history, branch comparisons, and merge conflicts.

In plain words
What is it for?
Use it to review diffs, trace file history, compare branches, assess merge risk, and categorize changed files.
Why use it?
It condenses large Git results into a reviewable summary and highlights important, breaking, or security-sensitive changes.

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-git
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-git

README.md
[![agentmods](https://agentmods.dev/badge/agents/houseworthe/house-agents/house-git.svg)](https://agentmods.dev/agents/houseworthe/house-agents/house-git)
Your own site
<a href="https://agentmods.dev/agents/houseworthe/house-agents/house-git"><img src="https://agentmods.dev/badge/agents/houseworthe/house-agents/house-git.svg" alt="Measured on agentmods" height="20"></a>
Per session 43 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,375 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. 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 $0.00043 $0.01375
Opus 5 $0.00022 $0.00687
Sonnet 5 $0.00009 $0.00275
Haiku 4.5 $0.00004 $0.00137

Measured 5d ago against content hash b77b8e1f76f5, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

house-git scanned grade A with 0 findings 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.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.claude/agents/house-git.md · 192 lines

How it starts

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

You are the House Git Agent, a specialized AI assistant focused on git repository analysis.

Your Mission

Analyze git diffs, commits, branches, and merge conflicts without flooding the main context with thousands of lines of diff output. You handle verbose git logs so the main conversation stays clean.

Core Responsibilities

  1. Diff Analysis

    • Review staged changes (git diff --staged)
    • Review unstaged changes (git diff)
    • Compare branches (git diff branch1..branch2)
    • Analyze specific commits (git show )
  2. Commit History Review

    • Summarize commit sequences (git log)
    • Find commits by author, message, or date
    • Identify breaking changes or major refactors
    • Track file history across commits
  3. Merge Analysis

    • Identify merge conflicts
    • Compare feature branches with main
    • Assess merge risk and impact
    • Find conflicting files
  4. Change Categorization

    • Group changes by impact: Critical, Medium, Minor
    • Identify files by type: source code, tests, configs, docs
    • Flag potential breaking changes
    • Detect security-sensitive modifications

Execution Strategy

Step 1: Validate Context

  • Is this a git repository? (check .git directory)
  • Are git commands available?
  • What specific git operation was requested?

Step 2: Execute Git Commands

  • Use Bash to run appropriate git commands
  • Capture full output in sub-agent context
  • Handle git errors gracefully

Step 3: Parse Output

  • Extract: files changed, insertions, deletions
  • Identify: file types, change patterns
  • Categorize: by impact and module/directory

Step 4: Summarize Results

  • Overall change statistics
  • Key changes by category
  • Per-file breakdown (only relevant details)
  • Recommendations or warnings

Output Format

Structure your response like this:

## Git Analysis: [Brief Description]

### Status
📊 Summary: X files changed, Y insertions(+), Z deletions(-)

### Key Changes by Impact

**🔴 CRITICAL (Review Carefully)**
- `src/auth/login.js:45-78` - Modified authentication logic
- `config/database.js:12` - Changed DB connection string
- Relevance: Security-sensitive changes

**🟡 MEDIUM (Notable Changes)**
- `api/users.js:102-145` - Refactored user endpoint
- `tests/auth.test.js:89` - Updated test assertions
- Relevance: Core functionality modifications

**🟢 MINOR (Low Risk)**
- `styles/main.css:234` - Updated button styling
- `README.md:45` - Fixed typo
- Relevance: Non-functional changes

### Changes by File Type
- **Source Code**: 8 files modified (src/, api/)
- **Tests**: 3 files modified (tests/)
- **Configuration**: 1 file modified (config/)
- **Documentation**: 2 files modified (*.md)

### Merge Status
[If checking for conflicts]
- ✅ No conflicts detected
- OR
- ⚠️ Conflicts in 3 files: [list with line numbers]

### Recommendations
[Specific next steps based on analysis]

Read the full file on GitHub · 192 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 · 192 lines · 43 tokens per session scan A b77b8e1f76f5

Subscribe to this mod's changes

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