What is homebutler CLAUDE.md?

A set of project instructions for Homebutler, a Go program that provides command-line, terminal, web-dashboard, and MCP-server interfaces for a small home server. It also defines rules for verification and written project contributions.

Use it when developing Homebutler to run its formatting, linting, tests, and build checks, and to write consistent Conventional Commit messages and contribution text.

It reduces unverified claims and inconsistent commits, pull requests, comments, and code comments. It gives contributors a shared standard for checking changes before saying they work.

How Higangssh/homebutler configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to Higangssh/homebutler. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/Higangssh/homebutler/main/CLAUDE.md

Clone the repo

git clone --depth 1 https://github.com/Higangssh/homebutler

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.

README.md

[![agentmods](https://agentmods.dev/badge/instructions/higangssh/homebutler/claude-md/github.svg)](https://agentmods.dev/instructions/higangssh/homebutler/claude-md)

Your own site

<a href="https://agentmods.dev/instructions/higangssh/homebutler/claude-md"><img src="https://agentmods.dev/badge/instructions/higangssh/homebutler/claude-md/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.

Your own site · 80×15

<a href="https://agentmods.dev/instructions/higangssh/homebutler/claude-md"><img src="https://agentmods.dev/badge/instructions/higangssh/homebutler/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 633 This file is loaded in full into every session.

When invoked 633 The same file — it is already loaded in full.

Security scan A 0 findings. 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.

Model	Per session	Once invoked
Fable 5.1	$0.00633	$0.00633
Opus 5.5	$0.00253	$0.00253
Sonnet 5.5	$0.00127	$0.00127
Haiku 4.5	$0.00063	$0.00063

Measured 1mo ago against content hash becb65152890, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

homebutler CLAUDE.md 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 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.

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.md · 74 lines

How it starts

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

homebutler

A single Go binary for running a small home server: CLI, TUI, web dashboard, and an MCP server, with no database and nothing running on the machines it watches.

Verify before claiming anything works

gofmt -w .
go vet ./...
golangci-lint run
go test ./...
go build ./...

All five must pass. go test ./... takes several minutes — internal/network and internal/remote wait on real timeouts — so start it early rather than running it last.

Writing commits, PRs, and comments

Everything written here is read by users, contributors, and future maintainers. Match the voice already in git log and CHANGELOG.md.

No tool attribution

Never add Co-Authored-By: Claude, Generated with Claude Code, 🤖 badges, "AI-assisted" notes, or any other tool signature to a commit message, PR description, issue comment, review comment, or code comment. The author is the person who decided the change should exist.

Commit subjects

Conventional Commits (feat:, fix:, docs:, refactor:, test:, chore:), lowercase after the type, no trailing period, no emoji.

Describe the behaviour that changed, not the mechanism. A fix: subject should read as the symptom a user would have hit:

fix: watch check called systemd and pm2 targets clean without checking them
fix: don't blame the host key when the TOFU connection fails
feat: cap incident history so the watch directory stops growing forever
docs: lead the README with what homebutler actually prints

Not fix: update watch.go, and not fix: add nil check in checkTarget.

Commit bodies

Only when the subject cannot carry it. Explain why the change is correct or what breaks without it — the diff already shows what changed. A one-line commit with a good subject is finished, not lazy.

Note user-visible behaviour changes explicitly. Someone upgrading needs to know that settings which were silently inert will now take effect.

PR descriptions and comments

Lead with what changed and why it matters. Keep the implementation notes to the decisions a reviewer could not infer from the diff — what you reused, what you deliberately left alone, what fails fast and where.

Read the full file on GitHub · 74 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.

1mo ago Changed · +5 tokens per session becb65152890
2mo ago First seen · 74 lines · 628 tokens per session scan A 4360033e7f3f

Subscribe to this mod's changes

homebutler CLAUDE.md is an instructions file published in the GitHub repository Higangssh/homebutler (314 stars, last pushed 5d ago), licensed MIT. It adds 633 tokens to every session, about $0.0025 per session on Opus 5.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.

DevOps and cloud Git and workflow Go Writing and docs ai cli docker go

homebutler CLAUDE.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
homebutler CLAUDE.mdHigangssh/homebutler	Instructions file	314	5d ago	MIT	A	633	Claude Code
vscode buildNext.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	9,719	GitHub Copilot
next.js AGENTS.mdvercel/next.js	Instructions file	143k	today	MIT	A	7,461	Codex, OpenCode
langchain AGENTS.mdlangchain-ai/langchain	Instructions file	149k	yesterday	MIT	A	4,680	Codex, OpenCode
vscode oss-third-party-notices.instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	5,516	GitHub Copilot
vscode copilot-instructions.mdmicrosoft/vscode	Instructions file	195k	yesterday	MIT	A	3,093	GitHub Copilot
deepseek-harness AGENTS.mddeepseek-ai/deepseek-harness	Instructions file	274k	2d ago	MIT	A	4,313	Codex, OpenCode

homebutler: Instructions file for Claude Code