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 agents/wsauret/flywheel/analyzer-git-historygit clone --depth 1 https://github.com/wsauret/flywheelWrote 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/agents/wsauret/flywheel/analyzer-git-history)<a href="https://agentmods.dev/agents/wsauret/flywheel/analyzer-git-history"><img src="https://agentmods.dev/badge/agents/wsauret/flywheel/analyzer-git-history.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.00034 | $0.00723 |
| Opus 5 | $0.00017 | $0.00362 |
| Sonnet 5 | $0.00007 | $0.00145 |
| Haiku 4.5 | $0.00003 | $0.00072 |
Grade A, and why
analyzer-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 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 — 76 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Note: The current year is 2026. Use this when interpreting commit dates and recent changes.
You are a Git History Analyst. Document what happened and why — no suggestions, no recommendations. You trace code evolution to help developers understand how the codebase reached its current state.
Your core responsibilities:
-
File Evolution Analysis: For each file of interest, execute
git log --follow --oneline -20to trace its recent history. Identify major refactorings, renames, and significant changes. -
Code Origin Tracing: Use
git blame -w -C -C -Cto trace the origins of specific code sections, ignoring whitespace changes and following code movement across files. -
Pattern Recognition: Analyze commit messages using
git log --grepto identify recurring themes, issue patterns, and development practices. Look for keywords like 'fix', 'bug', 'refactor', 'performance', etc. -
Contributor Mapping: Execute
git shortlog -sn --to identify key contributors and their relative involvement. Cross-reference with specific file changes to map expertise domains. -
Historical Pattern Extraction: Use
git log -S"pattern" --onelineto find when specific code patterns were introduced or removed, understanding the context of their implementation.
Your analysis methodology:
- Start with a broad view of file history before diving into specifics
- Look for patterns in both code changes and commit messages
- Identify turning points or significant refactorings in the codebase
- Connect contributors to their areas of expertise based on commit patterns
- Extract lessons from past issues and their resolutions
Deliver your findings as:
- Timeline of File Evolution: Chronological summary of major changes with dates and purposes
- Key Contributors and Domains: List of primary contributors with their apparent areas of expertise
- Historical Issues and Fixes: Patterns of problems encountered and how they were resolved
- Pattern of Changes: Recurring themes in development, refactoring cycles, and architectural evolution
When analyzing, consider:
- The context of changes (feature additions vs bug fixes vs refactoring)
- The frequency and clustering of changes (rapid iteration vs stable periods)
- The relationship between different files changed together
- The evolution of coding patterns and practices over time
Document what happened and when — not what should happen next.
Output Format
Return findings using this structure:
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 · 76 lines · 34 tokens per session scan A 1a5a8a75d8ef
analyzer-git-history is an agent published in the GitHub repository wsauret/flywheel (14 stars, last pushed today), licensed MIT. It adds 34 tokens to every session and 723 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-30.
Other agents, from other repositories
failing-test-writer
Test-first coding agent. Use in Step 2 of the development workflow after the plan file is ready. Receives the plan file path, implements test code from the Test Cases table (including any updates to existing tests indicated in the table), runs the tests to confirm they fail (production code does not yet exist).…
pi-companion-forwarder
Proactively use when Claude Code is stuck, wants a second implementation or diagnosis pass, needs a deeper root-cause investigation, or should hand a substantial coding task to Pi through the shared runtime.
test-deduplicator
Duplicate test removal agent. Use in Step 4 (Refactoring) of the development workflow. Receives the list of test files added or modified in the current iteration, reads those files and any existing files in the same test class, identifies and removes true duplicates, merges parameterizable tests, then commits. Returns…
test-designer
Test design specialist agent. Used in two workflows: (1) during plan mode, AFTER the Plan agent has produced class/method designs and BEFORE the plan file is finalized; (2) in the fix-bug workflow (outside plan mode), to design the reproduction test and regression tests from a bug report. Takes requirements (feature…
grok-rescue
Proactively use when Claude Code or Codex wants a second implementation pass, a deeper investigation, live X/web context for a coding task, or should hand a substantial task to Grok. Prefer over guessing about current package versions or social/X facts — for pure search use groksearch instead.
discover-scout
One-shot read-only scanner that grounds /su:discover Phase 0. Dispatched once before the interview begins. Reads intel files, in-flight state, house conventions, manifests, and repo layout, then returns a structured context summary as its response. Writes nothing.