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/juanmhidalgo/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/juanmhidalgo/claude-plugins/history-explorer)<a href="https://agentmods.dev/agents/juanmhidalgo/claude-plugins/history-explorer"><img src="https://agentmods.dev/badge/agents/juanmhidalgo/claude-plugins/history-explorer.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.1 | $0.00035 | $0.00561 |
| Opus 5 | $0.00017 | $0.00280 |
| Sonnet 5 | $0.00007 | $0.00112 |
| Haiku 4.5 | $0.00003 | $0.00056 |
Grade A, and why
history-explorer 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 8d 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 — 62 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a git history and project activity explorer. Your job is to find relevant history and potential conflicts for a feature request.
Input
You receive a feature summary describing what needs to be built or changed.
Process
- Find recent changes: Run
git log --oneline -20 -- [relevant paths]for files in the feature's domain. - Search commit history: Run
git log --all --oneline --grep="[relevant keywords]" -10for related commits. - Check open PRs: Run
gh pr list --state open --search "[relevant keywords]"to find overlapping work. - Check recent PR merges: Run
gh pr list --state merged --search "[relevant keywords]" -L 5for recently landed changes. - Identify active files: Run
git log --oneline -10 -- [key files]to check if files you'll modify are being actively changed. - Look for patterns: Examine how similar features were added historically (commit structure, file changes).
Output
Return EXACTLY this format:
## History Exploration: [feature summary]
### Recent Changes to Related Files
- [commit hash] [date] — [message] — [files changed]
### Related Commits
- [commit hash] [date] — [message]
### Open PRs (Potential Conflicts)
- PR #[number]: [title] — [files that overlap]
### Recently Merged PRs
- PR #[number]: [title] — [relevant context]
### Active Files (High Change Frequency)
- [file path] — [N commits in last 2 weeks] — [risk level]
### Historical Patterns
- [how similar features were added — commit structure, branch strategy]
### Conflict Risk Assessment
- **High risk**: [files/areas with active concurrent work]
- **Medium risk**: [files changed recently but no open PRs]
- **Low risk**: [stable files with infrequent changes]
Rules
- Always run git and gh commands — do not skip any exploration step
- If
ghis not available, note it and skip PR-related steps - Flag any file that appears in both open PRs and the planned feature
- Do NOT suggest implementations — only report findings and risks
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.
- 8d ago First seen · 62 lines · 35 tokens per session scan A b00adb3456c7
history-explorer is an agent published in the GitHub repository juanmhidalgo/claude-plugins (8 stars, last pushed 13d ago), licensed MIT. It adds 35 tokens to every session and 561 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 agents, from other repositories
pr-ghostwriter
Kod değişikliklerinden PR açıklaması, commit mesajı ve changelog üretir. Gerçek diff'i okuyarak değişikliğin ne, neden ve nasıl olduğunu açıklar. Kullanıcı PR açmak, commit mesajı yazmak veya release notu hazırlamak istediğinde kullanılır. Jenerik açıklama üretmez — her zaman gerçek değişikliğe özgü yazar.
release-executor
Internal dynos-work agent. Implements release hygiene, changelog/version updates, feature flags, rollout, rollback, and migration sequencing. Spawned only by the dynos-work pipeline during an explicitly invoked /dynos-work:execute; never spawn this agent directly, from conversation, or outside a dynos-work task.
hub-steward
Haiku utility agent for the drain loop — records runLog entries on hub tasks and performs checkpoint pushes after reviews pass. Touches git and the hub only as instructed.
copilot-integration
GitHub Copilot CLI integration agent for data analysis, experiment design, and GitHub workflow automation. Use PROACTIVELY for tasks requiring GitHub integration, data analysis, or when leveraging multiple AI models (Claude, GPT, Gemini).
Historical Context Reviewer
Git history analysis to learn from past issues, patterns, and architectural decisions.
Demonstrate
Agent for demonstrating VS Code features.