git-status

A plain-language summary of a Git repository, the folder where a project's tracked history and files are stored. It shows the current branch, changed files, and differences from the main branch.

In plain words
What is it for?
Use it before reviewing work, committing changes, or asking someone else to inspect the repository. It helps identify local edits and differences from the main branch.
Why use it?
It gives you a quick view of what has changed and where you are working without checking several Git commands yourself.

Command 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 commands/nodnarbnitram/claude-code-extensions/git-status
Clone the repo
git clone --depth 1 https://github.com/nodnarbnitram/claude-code-extensions

Made for: Claude Code.

Per session 8 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 88 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.00008 $0.00088
Opus 5 $0.00004 $0.00044
Sonnet 5 $0.00002 $0.00018
Haiku 4.5 $0.00001 $0.00009

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

Security

Grade A, and why

git-status 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 2d 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/commands/git-status.md · 17 lines

What it actually says

Git Status

Read the Files and run the Commands and summarize the current state of the git repository.

Commands

  • Current Status: !git status
  • Current diff: !git diff HEAD origin/main
  • Current branch: !git branch --show-current

Files

@README.md

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. 2d ago First seen · 17 lines · 8 tokens per session scan A 72772585801b

Subscribe to this mod's changes

git-status is a command published in the GitHub repository nodnarbnitram/claude-code-extensions (16 stars, last pushed 4mo ago), licensed MIT. It adds 8 tokens to every session and 88 once invoked, about $0.0000 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.