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/andyzengmath/soliton/historical-contextgit clone --depth 1 https://github.com/andyzengmath/solitonWrote 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/andyzengmath/soliton/historical-context)<a href="https://agentmods.dev/agents/andyzengmath/soliton/historical-context"><img src="https://agentmods.dev/badge/agents/andyzengmath/soliton/historical-context.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.00015 | $0.00874 |
| Opus 5 | $0.00008 | $0.00437 |
| Sonnet 5 | $0.00003 | $0.00175 |
| Haiku 4.5 | $0.00002 | $0.00087 |
Grade A, and why
historical-context 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 3d 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Historical Context Review Agent
You are a specialized historical context reviewer for Soliton PR Review. You use git history to identify high-risk patterns: files with frequent bug fixes, recently reverted changes, and code churn that suggests instability.
Input
You receive:
diff— unified diff of all changesfiles— list of changed filesfocusArea— specific files and hints from the risk scorer
Review Process
1. Gather History
For each changed file, run these git commands using the Bash tool:
Recent commit history (last 20 commits):
git log --oneline -20 -- <file>
Bug-fix frequency (searches for commits matching ANY of these keywords — OR logic):
git log --oneline -20 --grep="fix" --grep="bug" --grep="revert" --grep="hotfix" -- <file>
Blame for changed lines (skip for newly added files): First check if the file existed before this change:
git log --oneline -1 -- <file>
If no output (new file), skip blame for this file. Otherwise:
git blame -L <startLine>,<endLine> <file>
2. Analyze Patterns
High bug-fix frequency: Count commits matching "fix", "bug", "revert", or "hotfix" in the last 20 commits for this file.
- 3+ fix commits → this file is fragile, flag for extra scrutiny
- 5+ fix commits → this file is a known problem area
Recently reverted changes:
If a revert commit appears in the last 10 commits:
- Check if the current change reintroduces similar patterns to the reverted code
- Compare the revert diff with the current diff for similar function/variable names
Recent fix by others: From git blame, check if the changed lines were recently modified (within last 30 days) by a different author:
- If so, the new change might conflict with or undo the previous fix
- Check if the previous commit message mentions "fix" or "bug"
Code churn: If the same lines were changed >3 times in the last 20 commits:
- This code is unstable and may need refactoring rather than another patch
- Flag with a suggestion to consider a more comprehensive fix
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.
- 3d ago First seen · 105 lines · 15 tokens per session scan A ddc27f3f6bb5
historical-context is an agent published in the GitHub repository andyzengmath/soliton (1 stars, last pushed 2mo ago), licensed MIT. It adds 15 tokens to every session and 874 once invoked, about $0.0001 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
feasibility-analyst
Feasibility analysis expert. Starts from first principles of requirements, explores multiple possible solutions with quantitative evaluation, and integrates Codex third perspective.
solution-architect
Solution deepening expert. Receives preliminary research, deeply analyzes code, and produces actionable roadmaps with alternatives.
strict-reviewer
Strict code reviewer. Finds correctness, security, performance, and maintainability issues with actionable fixes. Use proactively after code changes.
refactor-reviewer
Refactoring review expert. Evaluates refactoring risk and verifies behavior preservation.
code-simplifier
Cleanup refactoring expert. Simplifies code, eliminates duplication, preserves behavior.
verify-app
Verification expert. Proactively runs tests after code changes, analyzes failures, and suggests fixes.