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 agentmods add skills/xiaolai/echo-sleuth-for-claude/git-miningnpx skills add xiaolai/echo-sleuth-for-claude --skill git-mininggit clone --depth 1 https://github.com/xiaolai/echo-sleuth-for-claudeWrote 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/xiaolai/echo-sleuth-for-claude/git-mining)<a href="https://agentmods.dev/skills/xiaolai/echo-sleuth-for-claude/git-mining"><img src="https://agentmods.dev/badge/skills/xiaolai/echo-sleuth-for-claude/git-mining.svg" alt="Measured on agentmods" 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 | $0.00065 | $0.00934 |
| Opus 5 | $0.00032 | $0.00467 |
| Sonnet 5 | $0.00013 | $0.00187 |
| Haiku 4.5 | $0.00006 | $0.00093 |
Grade A, and why
git-mining 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 3d 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 — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Git Mining — Code History Integration
Prerequisite Check
Before using git commands, verify the project is a git repo:
git rev-parse --git-dir 2>/dev/null && echo "IS_GIT_REPO" || echo "NOT_GIT_REPO"
If not a git repo, skip all git-related analysis and rely on JSONL data only.
Scripts
Cluster commits into work sessions
bash ${CLAUDE_PLUGIN_ROOT}/scripts/git-sessions.sh [repo-path] [--since "14 days ago"] [--gap 3600]
Full structured context dump
bash ${CLAUDE_PLUGIN_ROOT}/scripts/git-context.sh [repo-path] [--since "7 days ago"] [--limit 30]
Key Git Commands for Agents
Recent commits with file changes
git log --pretty=format:"%h|%ai|%s" --numstat --since="14 days ago" -30
File history (survives renames)
git log --oneline --follow -- path/to/file.ts
Symbol archaeology (when was X introduced?)
git log --oneline -S "FunctionName" # exact string
git log --oneline -G "pattern.*regex" # regex in diff
Hotspot files (most frequently changed)
git log --name-only --pretty=format: --since="30 days ago" | grep -v '^$' | sort | uniq -c | sort -rn | head -15
Commit message search
git log --oneline --grep="keyword" -i
What changed in a file recently
git log -p --follow --since="7 days ago" -- path/to/file.ts
Correlating Git Commits with Claude Sessions
Git commits made during Claude Code sessions cluster together in time (typically 60-440 seconds apart). Cross-session gaps are 1+ hours.
Method 1: Timestamp matching
Compare sessions-index.json entries (created/modified fields) with git commit timestamps (git log --pretty=format:"%at") to find which commits were made during which sessions.
Method 2: Conventional commit patterns
Claude Code sessions typically produce commit sequences like:
feat:→fix:→fix:→docs:→release:(complete cycle)fix:→test:(debugging session)refactor:→style:(cleanup session)
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 3d ago First seen · 97 lines · 65 tokens per session scan A 4f6debfa767b
git-mining is a skill published in the GitHub repository xiaolai/echo-sleuth-for-claude (9 stars, last pushed 10d ago), licensed ISC. It adds 65 tokens to every session and 934 once invoked, about $0.0003 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…