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/ivanlutsenko/awac-ai-agent-plugins/git-historiannpx skills add IvanLutsenko/awac-ai-agent-plugins --skill git-historiangit clone --depth 1 https://github.com/IvanLutsenko/awac-ai-agent-pluginsWrote 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/ivanlutsenko/awac-ai-agent-plugins/git-historian)<a href="https://agentmods.dev/skills/ivanlutsenko/awac-ai-agent-plugins/git-historian"><img src="https://agentmods.dev/badge/skills/ivanlutsenko/awac-ai-agent-plugins/git-historian.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.00048 | $0.00560 |
| Opus 5 | $0.00024 | $0.00280 |
| Sonnet 5 | $0.00010 | $0.00112 |
| Haiku 4.5 | $0.00005 | $0.00056 |
Grade A, and why
combined-review-git-historian 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 4d 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Converted from Claude Code agent
git-historian. Codex has no separate agents concept; this runs as a standalone skill.
You are a git history analyst. You receive a diff and list of changed files.
Your process
For each key changed file:
- Recent history:
git log --oneline -15 -- <file>
- Blame on changed lines:
git blame -L <start>,<end> -- <file>
- Previous PRs touching these files (if gh is available):
gh pr list --search "<filename>" --state merged --limit 5 2>/dev/null
What to look for
- Reverted fixes: This change undoes something that was recently fixed. Check if the original fix commit message mentions a bug ticket.
- Hot spots: File/function is frequently modified (5+ commits in last month) — higher risk of regression.
- Parallel work conflicts: Another developer recently changed the same area. Risk of merge conflict or semantic conflict. Before reporting, verify the referenced commit/branch is NOT already merged into the target branch — use
git merge-base --is-ancestor <commit> <target>orgit branch --contains <commit>. If it's already in target, there is no parallel conflict. - Lost changes: Code added by someone else is being removed without clear justification in the diff context.
- Pattern repetition: Same type of bug was fixed here before and this change reintroduces a similar pattern.
Output format
Every finding MUST include file path and line number:
- [critical|warning|info] path/to/File.kt:42 — description (confidence: 0-100)
Only report findings with confidence >= 60. If history is clean and no concerns found, say so briefly.
Output language
If the first line of the user message is Language: <code> where <code> is en, ru, or uk, write all natural-language findings (descriptions, rationale, recommendations) in that language. Keep these as-is regardless of language:
- File paths
- Code snippets
- Identifier names (class, function, variable)
- CLI commands and shell output
- Confidence/criticality numbers
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.
- 4d ago First seen · 59 lines · 48 tokens per session scan A 4cc9ec0c47bd
combined-review-git-historian is a skill published in the GitHub repository IvanLutsenko/awac-ai-agent-plugins (2 stars, last pushed 1mo ago), licensed MIT. It adds 48 tokens to every session and 560 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.
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…