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 Smirnov-Labs/claude-skills --skill git-recongit clone --depth 1 https://github.com/Smirnov-Labs/claude-skillsWrote 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/smirnov-labs/claude-skills/git-recon)<a href="https://agentmods.dev/skills/smirnov-labs/claude-skills/git-recon"><img src="https://agentmods.dev/badge/skills/smirnov-labs/claude-skills/git-recon/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/smirnov-labs/claude-skills/git-recon"><img src="https://agentmods.dev/badge/skills/smirnov-labs/claude-skills/git-recon.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.00099 | $0.02156 |
| Opus 5 | $0.00049 | $0.01078 |
| Sonnet 5 | $0.00020 | $0.00431 |
| Haiku 4.5 | $0.00010 | $0.00216 |
Grade A, and why
git-recon 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 11d 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.
How it starts
The opening of the file, as written. The whole thing — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Recon
Before reading code, read the git history. Five commands reveal where risk concentrates, who owns what, and whether the team is shipping or firefighting. Based on Piechowski's "5 git commands before reading code" (https://piechowski.io/post/git-commands-before-reading-code/).
When to Use
- Onboarding to an unfamiliar or inherited codebase
- Due diligence on an acquisition or handoff
- Planning a refactor and needing to locate risk
- User asks "what's the state of this repo?" or "where are the landmines?"
Prerequisites
Run from inside a git repository on the branch the user cares about (usually default). If any check fails, stop and ask the user.
git rev-parse --is-inside-work-tree # must print true
git rev-parse --is-shallow-repository # must print false — shallow clones distort all probes
git rev-parse --abbrev-ref HEAD # confirm branch scope in the report
Horizon: all probes use a single 12-month window for comparability. If the user wants a different window, override SINCE everywhere, don't mix.
SINCE="1 year ago"
Pipeline
Run all five probes (in parallel when possible), then synthesize. Do not just dump command output — the value is in the cross-referencing.
1. High-Churn Files — where change concentrates
git log --no-merges --since="$SINCE" --format=format: --name-only \
| grep -v '^$' \
| sort | uniq -c | sort -nr | head -20
Top 20 most-modified files in the last 12 months. Files that change constantly are risky: unpredictable blast radius, likely god-objects or missing abstractions.
Caveat — renames: this command is not rename-aware. A file renamed mid-window splits its churn across old and new paths. When drilling into a specific top file, rerun with git log --follow --no-merges --since="$SINCE" -- <path> to see true lifetime churn.
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.
- 11d ago First seen · 146 lines · 99 tokens per session scan A ad50501ed1d6
git-recon is a skill published in the GitHub repository Smirnov-Labs/claude-skills (5 stars, last pushed 2mo ago), licensed MIT. It adds 99 tokens to every session and 2,156 once invoked, about $0.0005 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.
Other skills, from other repositories
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
changelog-composer
Generates structured changelogs and release notes from git history and PRs, classifying breaking changes, features, fixes, performance, docs. Triggers on: "generate changelog", "write release notes", "what changed since", "prepare release", "release notes for", "diff since tag".
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…