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 Goldziher/basemind --skill basemind-git-historygit clone --depth 1 https://github.com/Goldziher/basemindWrote 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/goldziher/basemind/basemind-git-history)<a href="https://agentmods.dev/skills/goldziher/basemind/basemind-git-history"><img src="https://agentmods.dev/badge/skills/goldziher/basemind/basemind-git-history/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/goldziher/basemind/basemind-git-history"><img src="https://agentmods.dev/badge/skills/goldziher/basemind/basemind-git-history.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00091 | $0.00980 |
| Opus 5 | $0.00046 | $0.00490 |
| Sonnet 5 | $0.00018 | $0.00196 |
| Haiku 4.5 | $0.00009 | $0.00098 |
Grade A, and why
basemind-git-history 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 9d 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 — 63 lines — stays where its author put it; the contents beside it link to each section on GitHub.
basemind-git-history — git intelligence over the index
basemind indexes git history and resolves blame and diffs at symbol resolution, backed by a
gix history index. History queries return commits, authors, paths, and line/symbol attributions —
structured and capped — for a fraction of the cost of parsing git log / git blame output.
basemind first, naked git fallback. Prefer these tools over shelling out to git log,
git blame, or git diff. Drop to raw git only when no tool covers the question (e.g. staging,
rebasing, anything that mutates history).
Tool routing
| Question | MCP tool | CLI |
|---|---|---|
| "What changed recently?" | git { mode: "recent" } |
basemind git recent [--limit N] |
| "Which commits touched path P?" | git { mode: "touching", path: P } |
basemind git touching P |
| "Path-filtered commit log?" | git { mode: "by_path", pattern: P } |
basemind git by-path P |
| "When did symbol X last change?" | git { mode: "symbol_history", path: F, name: X } |
basemind git symbol-history F X |
| "Who wrote this line?" | git { mode: "blame", path: F } |
basemind git blame F |
| "Who wrote this symbol / when did its body change?" | git { mode: "blame_symbol", path: F, name: X } |
basemind git blame-symbol F X |
| "Diff a file between revs?" | git { mode: "diff", path: F, rev_old, rev_new } |
basemind git diff F old new |
| "What symbols did a branch add/remove?" | git { mode: "diff_outline", path: F, rev } |
basemind git diff-outline F [--rev] |
| "Where's the churn?" | git { mode: "churn" } |
basemind git churn [--top-k N] |
| "What's dirty in the working tree?" | git { mode: "status" } |
basemind git status |
| "What's HEAD / branch / origin?" | admin { mode: "repo" } |
basemind admin repo |
| "Full-text search commit messages + authors?" | git { mode: "search", pattern: "…" } |
basemind git search "…" |
Examples
git { mode: "recent", limit: 5 }
→ 612df7e chore(release): v0.15.0
1779b99 fix(git-history,serve): address code-review findings
...
git { mode: "blame_symbol", path: "src/scanner.rs", name: "process_file" }
→ last touched by <author> in <commit> — body hash changed at HEAD~7
git { mode: "diff_outline", path: "src/mcp/tools.rs", rev: "HEAD~5" }
→ + search_history (function) - old_helper (function)
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.
- 9d ago First seen · 63 lines · 91 tokens per session scan A 4a329be938fc
basemind-git-history is a skill published in the GitHub repository Goldziher/basemind (99 stars, last pushed 7d ago), licensed MIT. It adds 91 tokens to every session and 980 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-30.
Other skills, from other repositories
sem
Use sem to get entity-level (function/class/method) semantic diffs, impact analysis, blame, and dependency context from any Git repo. Trigger this skill whenever the user asks what changed in a commit or PR, wants to understand the blast radius of a change, needs to know who last modified a function, wants to trace…
sem
Semantic version control CLI. Entity-level diffs for Git (functions, classes, methods instead of lines).
trace-mcp-pre-commit
Run trace-mcp security, quality-gate, and antipattern checks before committing or opening a PR. Activate when the agent is about to create a commit or pull request in a project indexed by trace-mcp.
commit
A commit candidate is the exact patch that will enter the commit. A coherent change has one task or issue as its reason for existing.
mastermind-audit-attestation
Generate, verify, sign, or explain Mastermind audit envelopes and GitHub attestations. Use when checking audit-bundle tampering, validating exact repository/baseline/head policy, working with detached Ed25519 signatures, reviewing CI provenance, or distinguishing content integrity from signer authenticity and policy…
memtrace-evolution
Trace source-code change history from Memtrace's symbol-level temporal memory. Use when the user asks about change history, recent modifications, what changed since a date, symbol timeline, evolution, unexpected changes, or incident timelines. Do not use git log, git diff, Grep, or manual file search to reconstruct…