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.
npx skills add autohandai/code-cli --skill git-analysisgit clone --depth 1 https://github.com/autohandai/code-cliWrote 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.
[](https://agentmods.dev/skills/autohandai/code-cli/git-analysis)<a href="https://agentmods.dev/skills/autohandai/code-cli/git-analysis"><img src="https://agentmods.dev/badge/skills/autohandai/code-cli/git-analysis/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.
<a href="https://agentmods.dev/skills/autohandai/code-cli/git-analysis"><img src="https://agentmods.dev/badge/skills/autohandai/code-cli/git-analysis.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00057 | $0.00437 |
| Opus 5.5 | $0.00023 | $0.00175 |
| Sonnet 5.5 | $0.00011 | $0.00087 |
| Haiku 4.5 | $0.00006 | $0.00044 |
Grade A, and why
git-analysis 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 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.
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.
What it actually says
Read the history, not just the tree
Git already knows most of what a reviewer wants to ask. Use it before reading code, and cite commits.
Techniques
- What changed between X and Y:
git_diff_range, then group by module; summarize behavior changes, not file lists. - Why does this line exist:
git blame -Lthroughrun_command, thengit showthe commit and read its message and the surrounding diff. - When did it break: find the last known good and first known bad, then
narrow with
git bisect run <test command>when a test exists; otherwise bisect by hand on the commits touching the area (git log -- <path>). - Who owns this area:
git shortlog -sn -- <path>and recent authors. - What is risky in this release: largest diffs, files with many recent touches, changes without tests, dependency bumps.
- Branch relationships:
git log --oneline --graph, merge bases, commits not yet in main.
Rules
- Quote commit hashes and dates; never paraphrase a commit message as fact without showing it.
- Read-only by default. Do not rebase, reset, or rewrite history unless the user asks for that specific operation and confirms.
- Large histories: bound queries with paths,
--since, and-n.
Output
A short narrative with the commits that matter, then a table of commit, date, author, summary, and the evidence line for each claim. End with the open questions the history cannot answer.
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 · 40 lines · 57 tokens per session scan A 8a7a6b5e04d6
git-analysis is a skill published in the GitHub repository autohandai/code-cli (205 stars, last pushed today), licensed Apache-2.0. It adds 57 tokens to every session and 437 once invoked, about $0.0002 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-09-15.
Other skills, from other repositories
git-flow
Use this skill when committing, branching, opening a pull request, resolving conflicts, or recovering from a git mistake in any repository. Triggers: user mentions "commit", "branch", "PR", "pull request", "merge", "rebase", "conflict", "stash", "cherry-pick", "revert", "bisect", "reflog", "force push".
commit
Create a commit following repository guidelines with proper versioning and changelog updates.
commit-standards
Guidelines for consistent, well-documented commits in SDD projects.
github-pr-workflow
Prepare a GitHub pull request from a feature branch — branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments.
agentic-jujutsu
Quantum-resistant, self-learning version control for AI agents with ReasoningBank intelligence and multi-agent coordination.
github-automation
GitHub workflow automation, PR management, issue tracking, and code review coordination. Integrates with GitHub Actions and repository management. Use when: PR creation, code review, issue management, release automation, workflow setup. Skip when: local-only changes, non-GitHub repositories.