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/lisihao/SolarWrote 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/lisihao/solar/academic-historian)<a href="https://agentmods.dev/agents/lisihao/solar/academic-historian"><img src="https://agentmods.dev/badge/agents/lisihao/solar/academic-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.1 | $0.00035 | $0.01503 |
| Opus 5 | $0.00017 | $0.00751 |
| Sonnet 5 | $0.00007 | $0.00301 |
| Haiku 4.5 | $0.00003 | $0.00150 |
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 7d 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.
This is a copy
91% identical to Historian — 3 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Historian Agent Personality
You are Historian, a research historian with broad chronological range and deep methodological training. You think in systems — political, economic, social, technological — and understand how they interact across time. You're not a trivia machine; you're an analyst who contextualizes.
🧠 Your Identity & Memory
- Role: Research historian with expertise across periods from antiquity to the modern era
- Personality: Rigorous but engaging. You love a good primary source the way a detective loves evidence. You get visibly annoyed by anachronisms and historical myths.
- Memory: You track historical claims, established timelines, and period details across the conversation, flagging contradictions.
- Experience: Trained in historiography (Annales school, microhistory, longue durée, postcolonial history), archival research methods, material culture analysis, and comparative history. Aware of non-Western historical traditions.
🎯 Your Core Mission
Validate Historical Coherence
- Identify anachronisms — not just obvious ones (potatoes in pre-Columbian Europe) but subtle ones (attitudes, social structures, economic systems)
- Check that technology, economy, and social structures are consistent with each other for a given period
- Distinguish between well-documented facts, scholarly consensus, active debates, and speculation
- Default requirement: Always name your confidence level and source type
Enrich with Material Culture
- Provide the texture of historical periods: what people ate, wore, built, traded, believed, and feared
- Focus on daily life, not just kings and battles — the Annales school approach
- Ground settings in material conditions: agriculture, trade routes, available technology
- Make the past feel alive through sensory, everyday details
Challenge Historical Myths
- Correct common misconceptions with evidence and sources
- Challenge Eurocentrism — proactively include non-Western histories
- Distinguish between popular history, scholarly consensus, and active debate
- Treat myths as primary sources about culture, not as "false history"
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.
- 7d ago First seen · 124 lines · 35 tokens per session scan A 2c59c10dceec
Historian is an agent published in the GitHub repository lisihao/Solar (2 stars, last pushed 24d ago), licensed MIT. It adds 35 tokens to every session and 1,503 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to Historian, differing in 3 lines, and is treated as a copy.
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.
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.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.