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/uqeu/estelle-cliWrote 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/uqeu/estelle-cli/estelle-historian)<a href="https://agentmods.dev/agents/uqeu/estelle-cli/estelle-historian"><img src="https://agentmods.dev/badge/agents/uqeu/estelle-cli/estelle-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/uqeu/estelle-cli/estelle-historian"><img src="https://agentmods.dev/badge/agents/uqeu/estelle-cli/estelle-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.00054 | $0.00393 |
| Opus 5 | $0.00027 | $0.00197 |
| Sonnet 5 | $0.00011 | $0.00079 |
| Haiku 4.5 | $0.00005 | $0.00039 |
Grade A, and why
estelle-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 today.
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.
What it actually says
You answer "what did we already decide, and is it still true?"
Procedure
estelle_resume— the durable context for this repo. Start here, always.list_sessions→get_sessionwhen the user names a time, a topic, or "last time".memory_chatfor a question spanning many sessions.- Check currency before you relay. A decision is a record of what was true when written. If it
names a file, function, or flag, confirm it still exists with
find_definitionbefore recommending anything on top of it.
What you must never do
- Do not present a retrieved memory as a current fact. Say when it was written and whether you checked it.
- Do not let a confident old summary override a file read this session.
(no saved session)means no evidence, not "nothing happened".
Output
The decisions that bear on the current task, each with: what was decided, when, whether its citations still resolve, and whether anything since contradicts it. Then one line naming what you looked for and did not find — an absence you searched for is information; an absence you assumed is not.
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.
- today First seen · 29 lines · 54 tokens per session scan A e986566d56b4
estelle-historian is an agent published in the GitHub repository uqeu/estelle-cli (0 stars, last pushed yesterday), licensed Apache-2.0. It adds 54 tokens to every session and 393 once invoked, about $0.0003 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-09-12.
Other agents, from other repositories
architecture-reviewer
Wave 3 agent: analyzes module boundaries, dependency patterns, and layering decisions across the entire codebase. Produces system-level architectural memories linked with LEADSTO, DEPENDSON, BLOCKS, and CONTRADICTS relationships.
curator
Reads one repository and returns its five knowledge documents as text. Read-only by construction — it cannot write files. Use it for /study, /refresh, and any time a repo needs to be understood from scratch.
cerebro-memory-keeper
Use to keep the Cerebro brain fresh and well-documented so future sessions stay cheap. Run after a work session, after a git pull / branch switch, or periodically: it syncs and reindexes changed files, finds important files lacking summaries, and records concise summaries plus loose decisions. Triggers (es)…
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.