git-review

A checklist for reviewing the changes in a Git repository, the system used to track code history and differences.

In plain words
What is it for?
It is for checking repository status, staged and unstaged differences, ignored files, relevant history, and whether the final set of changes is safe to commit.
Why use it?
It helps find accidental edits, exposed secrets, unrelated files, risky dependency or database changes, and missing tests or documentation before committing.

Skill for Claude CodeCodex

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 skills/arnosdeus/agent-toolkit/git-review
Any agent
npx skills add Arnosdeus/agent-toolkit --skill git-review
Clone the repo
git clone --depth 1 https://github.com/Arnosdeus/agent-toolkit

Made for: Claude Code, Codex.

Per session 30 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 177 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.00030 $0.00177
Opus 5 $0.00015 $0.00088
Sonnet 5 $0.00006 $0.00035
Haiku 4.5 $0.00003 $0.00018

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

Security

Grade A, and why

git-review 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.

skills/git-review/SKILL.md · 19 lines

What it actually says

Git Review

Procedure and output

Review status, staged and unstaged diffs, tracked paths, and the final commit boundary. Report BLOCKER, MAJOR, MINOR, or NOTE findings as path — issue — evidence — action, then state whether the tree is safe to commit.

Inspect status, staged and unstaged diffs, changed files, ignored files, and history relevant to the task. Check for secrets, generated output, unrelated changes, dependency or lockfile changes, migrations, tests, and documentation. Never reset work, force-push, rewrite history, or delete unrelated changes unless explicitly instructed. Report any remaining uncertainty.

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 · 19 lines · 30 tokens per session scan A 6b3233c084be

Subscribe to this mod's changes

git-review is a skill published in the GitHub repository Arnosdeus/agent-toolkit (2 stars, last pushed 9d ago), licensed MIT. It adds 30 tokens to every session and 177 once invoked, about $0.0002 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-31.

Related

Other skills, from other repositories

opensrc

Fetch dependency source code to give AI agents deeper implementation context. Use when the agent needs to understand how a library works internally, read source code for a package, fetch implementation details for a dependency, or explore how an npm/PyPI/crates.io package is built. Triggers include "fetch source for"…

vercel-labs/opensrc · 103 tokens

release-cli

Release a new version of the tokenmaxxing CLI to npm. Use when explicitly asked to release or publish @851-labs/tokenmaxxing, including checking main, bumping apps/cli/package.json, updating CHANGELOG.md, committing, tagging cli-vX.Y.Z, pushing, monitoring generated native package publishing, and smoke testing the…

851-labs/tokenmaxxing · 73 tokens

first-plan-co-change-analysis

Skill que constrói o Co-change Graph - "quando arquivo X muda, qual outro arquivo geralmente muda junto?". Use durante Discovery e em /fp:cochange. Baseado em git history. Detecta arquivos co-dependentes que devem ser editados juntos para evitar PRs incompletos. v0.3.0+ usa engine nativo Rust quando disponível…

vynazevedo/first-plan · 88 tokens

first-plan-provenance-tracker

Skill que define o schema de proveniência e o sistema de freshness tracking para findings em .first-plan/. Use durante Discovery e refresh para registrar source (file:line@SHA), TTL, confidence inicial e cadeia de supersedeção. Aplica decay de confidence baseado em idade.

vynazevedo/first-plan · 64 tokens

first-plan-protocol

Esta skill DEVE ser carregada em qualquer comando do plugin first-plan. Define o protocolo PLAN-FIRST (Discovery -> Plan -> Approval -> Execution -> Report), as 7 regras invioláveis e o comportamento esperado em cada fase. Ative quando o usuário invocar /fp: ou mencionar "first-plan", "context compilation", "discovery…

vynazevedo/first-plan · 81 tokens

first-plan-reconciliation

Skill que define Spec-Code Reconciliation - matching contínuo entre artefatos de intenção (docs, specs, JIRA, GitHub issues) e implementação (código, testes, PRs). Use durante Discovery e em /fp:check para identificar feature ja implementada, em flight, drifted ou abandonada.

vynazevedo/first-plan · 70 tokens