What is cli CLAUDE.md?

Project instructions for git-treeline/cli, a Go command-line tool for managing services, ports, and databases across parallel Git worktrees. A Git worktree is a separate working directory connected to the same repository.

Use them when changing CLI commands, writing table-driven Go tests, running the project's checks, building the tool, or updating its README.

They give coding agents the project's required commands, testing rules, code conventions, and documentation update policy.

How git-treeline/cli configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to git-treeline/cli. 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/git-treeline/cli/main/CLAUDE.md

Clone the repo

git clone --depth 1 https://github.com/git-treeline/cli

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/git-treeline/cli/claude-md/github.svg)](https://agentmods.dev/instructions/git-treeline/cli/claude-md)

Your own site

<a href="https://agentmods.dev/instructions/git-treeline/cli/claude-md"><img src="https://agentmods.dev/badge/instructions/git-treeline/cli/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/git-treeline/cli/claude-md"><img src="https://agentmods.dev/badge/instructions/git-treeline/cli/claude-md.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 630 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.00630	$0.00630
Opus 5.5	$0.00252	$0.00252
Sonnet 5.5	$0.00126	$0.00126
Haiku 4.5	$0.00063	$0.00063

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

Security

Grade A, and why

cli 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 2mo 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 · 70 lines

How it starts

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

git-treeline CLI — agent guide

Go CLI for worktree environment management. Allocates ports, databases, and services across parallel git worktrees; exposes an MCP server for AI agent integration.

Stack

Go 1.26+
Cobra for CLI structure (cmd/)
bubbletea/v2 for TUI components
mcp-go for the MCP server (cmd/serve.go)

Development

make ci          # lint + test (installs golangci-lint and govulncheck if absent)
go test ./...    # tests only
go build .       # build the binary

Testing conventions

Prefer pure extraction over dependency injection — see CONTRIBUTING.md for the full hierarchy. New commands need table-driven tests in cmd/<name>_test.go. Run go test ./cmd/... after any cmd/ change; run go test ./... before opening a PR.

README update policy

README.md is the canonical user-facing reference. Keep it accurate; it is not auto-generated.

Update the README when a PR:

Adds a new command (add a row to the CLI reference table and, if the command warrants it, a numbered section in Quick start)
Adds a flag to an existing command (add it to the flags column of that command's row in the CLI reference table)
Changes a flag's name or behavior in a user-visible way
Adds or changes a .treeline.yml field (update the project config fields table)
Adds or changes a user config key (update the user config section)
Adds or changes an interpolation token (update the tokens table)
Changes the behavior of an existing command in a way that contradicts the current docs

Do not update the README for:

Bug fixes that restore documented behavior
Internal refactors with no user-visible surface change
Dependency bumps
CI / workflow changes
Test-only changes

How to update:

CLI reference table (bottom of README): one row per command, format | \gtl ` | `--flag1` `--flag2` | Description |. Keep flags in roughly the order they appear in --help`. Use backtick-wrapped flag names.
Quick start numbered sections: only add a new section for commands a new user would encounter early. Networking, database, and advanced lifecycle commands already have sections; don't duplicate them. Extend an existing section when adding a flag to a well-known command.
Config tables: mirror the field names and types exactly as they appear in the Go structs — don't invent defaults that aren't enforced in code.

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

2mo ago First seen · 70 lines · 630 tokens per session scan A f35eeac21a37

Subscribe to this mod's changes

cli CLAUDE.md is an instructions file published in the GitHub repository git-treeline/cli (6 stars, last pushed 5d ago), licensed MIT. It adds 630 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-31.

cli CLAUDE.md next to 6 instructions from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
cli CLAUDE.mdgit-treeline/cli	Instructions file	6	5d ago	MIT	A	630	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	yesterday	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

cli: Instructions file for Claude Code