A read-only audit and guided setup process for Git, the version-control tool used to track code changes. It checks identity, editor, diff, merge, and optional signing or repository-safety settings before proposing changes.

Use it to check Git configuration, set your name and email, configure editing and comparison tools, or address signing and safe-repository issues when requested.

It reveals missing or inconsistent Git settings without overwriting existing preferences. Changes are suggested and applied only after confirmation.

git-setup — Skill for Claude Code by microsoft/hve-core

About the project

HVE Core is a collection of agents, prompts, coding instructions, and skills for building repeatable software-development workflows with GitHub Copilot. It is intended for individuals and teams that want structured AI-assisted research, planning, implementation, and review, while the catalogue entries provide many of its reusable workflow components.

microsoft/hve-core · 1,606 stars · on GitHub

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.

Any agent

npx skills add microsoft/hve-core --skill git-setup

Clone the repo

git clone --depth 1 https://github.com/microsoft/hve-core

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/skills/microsoft/hve-core/git-setup/github.svg)](https://agentmods.dev/skills/microsoft/hve-core/git-setup)

Your own site

<a href="https://agentmods.dev/skills/microsoft/hve-core/git-setup"><img src="https://agentmods.dev/badge/skills/microsoft/hve-core/git-setup/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/skills/microsoft/hve-core/git-setup"><img src="https://agentmods.dev/badge/skills/microsoft/hve-core/git-setup.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 54 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,881 The whole file, excluding the scripts and references it only reads on demand.

Security scan B 1 finding. 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.00054	$0.01881
Opus 5.5	$0.00022	$0.00752
Sonnet 5.5	$0.00011	$0.00376
Haiku 4.5	$0.00005	$0.00188

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

Security

Grade B, and why

git-setup scanned grade B 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 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.

Reaches for credential filesmediumPrivilege escalation

SSH keys, cloud credentials, git-credentials, .npmrc, /etc/shadow: reading these is how a config file becomes a credential leak.

git config --global user.signingkey "~/.ssh/id_ed25519.pub"

Downgraded: this mod is about security review, or the phrase is quoted, so it is likely naming the pattern rather than instructing it.

.github/skills/hve-core/git-setup/SKILL.md · 166 lines

How it starts

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

Git Setup

Goal

Help the user configure Git consistently for everyday work (add, commit, fetch, pull, push) without overwriting preferred settings. Verify current values before suggesting changes, and never modify configuration without explicit confirmation.

Scope:

Identity: user.name and user.email are set.
Editing, diff, and merge tooling is configured when currently unset.
Commit signing (GPG or SSH) help happens only when the user asks for it or reports a signing error.
A safe.directory entry is proposed only when the user reports a Git ownership or unsafe-repository error.
Existing customizations stay intact; never downgrade or remove settings.

Flow

Audit the current configuration with exactly one command: git config --list --show-origin. It captures values and their source files. Run no other lookup, gpg, or ssh-keygen command during the audit.
Report gaps and desirable improvements from that output.
Propose minimal remediation commands, grouped logically.
Ask for confirmation per group before applying it, and apply only confirmed groups.
Verify applied settings with single git config --get <key> reads and show a before and after summary.
Summarize applied changes and remaining optional improvements.

Detection

Classify each area from the baseline output only, in this order:

Identity: parse user.name and user.email and note each scope from its origin path. Mark a value missing when no scope sets it.
Commit signing (passive scan): parse commit.gpgSign, gpg.format, and user.signingkey, and classify the result for display only:
- Disabled: commit.gpgSign is false or unset.
- Configured candidate: signing is true and both gpg.format and user.signingkey are present.
- Incomplete: signing is true but gpg.format or user.signingkey is missing.
- Not configured: all three are unset.
Editor and tools: parse core.editor, diff.tool, and merge.tool, and mark each missing value as a gap.
Safe directory: note whether any safe.directory entry includes the current repository path.
Line endings: parse core.autocrlf and core.eol, and flag them only when both are unset and the user mentions cross-platform needs.

Read the full file on GitHub · 166 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 First seen · 166 lines · 54 tokens per session scan B a883d8c9ab30

Subscribe to this mod's changes

git-setup is a skill published in the GitHub repository microsoft/hve-core (1,606 stars, last pushed today), licensed MIT. It adds 54 tokens to every session and 1,881 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it B with 1 finding (reaches for credential files). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-10-08.

Git and workflow

git-setup next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
git-setupmicrosoft/hve-core	Skill	1.6k	today	MIT	B	54	Claude Code
merge-batchdiegosouzapw/OmniRoute	Skill	85k	today	MIT	A	46	Claude Code
prowler-commitprowler-cloud/prowler	Skill	15k	today	Apache-2.0	A	44	Claude Code, Codex
gh-auth-isolationgithub/gh-aw	Skill	5.6k	today	MIT	A	20	Claude Code, Codex
comet-githubrpamis/comet	Skill	3.3k	today	MIT	A	72	Claude Code, Codex
github-skillzeenie-ai/OpenCompany	Skill	1.1k	3d ago	MIT	A	51	Claude Code
re0-mergeLilMGenius/paperthin	Skill	1.4k	today	MIT	A	70	Claude Code

git-setup