GIT_COLLABORATION

A repository-work checklist for coding agents, backed by project rules in specific documentation files.

In plain words
What is it for?
Use it before and during repository work to inspect changes, identify owned files, choose valid topic branches, and follow the project's development rules.
Why use it?
It reduces accidental changes to files another person owns and keeps branch, scope, and safety decisions consistent.

Agent

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/heretyc/subagent-mcp/git_collaboration
Clone the repo
git clone --depth 1 https://github.com/Heretyc/subagent-mcp
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 713 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.00000 $0.00713
Opus 5 $0.00000 $0.00357
Sonnet 5 $0.00000 $0.00143
Haiku 4.5 $0.00000 $0.00071

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

Security

Grade A, and why

GIT_COLLABORATION 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 yesterday.

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.

agents/GIT_COLLABORATION.md · 73 lines

How it starts

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

Agent Git Collaboration Checklist

Use this checklist for repository work. The normative policy is docs/spec/dev-loop/git-collaboration.md; AGENTS.md holds root invariants.

Before Work

  1. Run git status --short --branch.
  2. Identify unowned dirty files. Do not overwrite, stage, commit, reset, clean, rebase, move, or hide them without explicit owner authorization.
  3. Follow docs/spec/safety-scope.md for interactive cascades, automated declarations, credential handling, and sub-agent prompts.
  4. Read the task scope and name the owned files or directories.
  5. Use a topic branch for non-trivial work unless the owner explicitly directed a different workflow that still respects protected/default-branch rules.

Branches

  • Branch names must pass git check-ref-format --branch.
  • Use <type>/<short-topic> or <type>/<actor>/<short-topic>.
  • Allowed types: feature, fix, hotfix, release, docs, test, refactor, chore, agent, user, integration, audit.
  • Use lowercase ASCII, digits, hyphen, underscore, period, and single slash separators only.
  • Do not reuse merged, closed, abandoned, or stale branches.
  • Do not force-push or rewrite shared history without explicit coordination.

Worktrees

  • Use at most one writable worktree per branch.
  • Put linked worktrees under a sibling worktree root, never inside another repository or worktree.
  • Before branch/worktree cleanup or force-updates, inspect git worktree list --porcelain -z.
  • Use git worktree remove for cleanup and do not remove unclean worktrees unless work is committed, preserved, or confirmed disposable.

Commits

  • Inspect the exact staged diff before committing.
  • Commit the smallest coherent logical unit.
  • Do not commit unrelated changes, conflict markers, secrets, debug output, generated noise, caches, large artifacts, or unverified work.
  • Add tests or validation for behavior changes, or record why not.
  • Do not add AI attribution or co-author lines.
  • Do not use --no-verify or empty commits unless policy explicitly requires it.

Read the full file on GitHub · 73 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. yesterday First seen · 73 lines · 0 tokens per session scan A eca97118d329

Subscribe to this mod's changes

GIT_COLLABORATION is an agent published in the GitHub repository Heretyc/subagent-mcp (3 stars, last pushed 4d ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 713 tokens. 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.