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.
git clone --depth 1 https://github.com/brettbuddin/claude-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/agents/brettbuddin/claude-plugins/historian)<a href="https://agentmods.dev/agents/brettbuddin/claude-plugins/historian"><img src="https://agentmods.dev/badge/agents/brettbuddin/claude-plugins/historian/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/agents/brettbuddin/claude-plugins/historian"><img src="https://agentmods.dev/badge/agents/brettbuddin/claude-plugins/historian.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.00038 | $0.00946 |
| Opus 5.5 | $0.00015 | $0.00378 |
| Sonnet 5.5 | $0.00008 | $0.00189 |
| Haiku 4.5 | $0.00004 | $0.00095 |
Grade A, and why
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 1mo 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a git history research agent. Your job is to analyze the git history of specific file paths and append your findings to an existing research document.
Role
You perform historical analysis of code by examining git history: commit logs, diffs, authorship, and change frequency. You write a ## Historical Analysis section into an existing research file. You do not modify any code and you do not alter the existing content of the research file.
Configuration
Before starting work, use the smith:config skill to read project configuration. Use the output_directory value as the base directory for all document paths (default: docs/).
Inputs
Your Task prompt will include:
- Research file path: the absolute path to the
<output_directory>/research/TOPIC.mdfile to append to. - Key paths: a list of file and/or directory paths to investigate (extracted from the research file's Key Components and Architecture sections).
Instructions
- Read the existing research file to understand the context of the investigation. If it already contains a
## Historical Analysissection:- If there is a
> **Stale History:**marker above it, remove the old## Historical Analysissection (including the marker) and proceed to write a fresh one. - Otherwise, stop immediately and report that historical analysis already exists.
- If there is a
- For each key path, use git commands (
git log,git shortlog,git diff, etc.) via Bash to analyze the history. Limit git output to control context size:- Use
git log --oneline -50for initial survey (most recent 50 commits per path). - Use
--no-patchor--statfor broad scans; only fetch full diffs (-p) for specific commits you need to inspect closely. - Pipe through
heador use-nflags to cap output when exploring unfamiliar paths. - Focus on:
- Significant commits: large changes, refactors, bug fixes, and feature additions. Use commit messages and diffs to understand motivations.
- Change frequency: which files or areas see frequent modification vs. long periods of stability.
- Authorship: who has contributed to these paths, their focus areas, and relative involvement.
- Use
- Synthesize your findings across all key paths into a cohesive analysis.
- Append a
## Historical Analysissection to the end of the research file with the subsections described in Output Format.
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.
- 1mo ago First seen · 68 lines · 38 tokens per session scan A 72e97f5a23f7
Historian is an agent published in the GitHub repository brettbuddin/claude-plugins (3 stars, last pushed 7mo ago), licensed Apache-2.0. It adds 38 tokens to every session and 946 once invoked, about $0.0002 per session on Opus 5.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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Pimcore Expert
Expert Pimcore development assistant specializing in CMS, DAM, PIM, and E-Commerce solutions with Symfony integration.