historian

A project-memory agent that records lessons from previous builds, including known mistakes, successful practices, and review findings. It produces structured briefings for other agents.

In plain words
What is it for?
It helps review past learnings before a build, provide guidance during implementation, and record specific fixes and recurring patterns afterward.
Why use it?
It helps later work avoid repeating documented problems and preserves decisions that might otherwise be forgotten.

Agent

Install

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.

agentmods
npx agentmods add agents/developer2013/bricks-mcp-open/historian
Clone the repo
git clone --depth 1 https://github.com/developer2013/bricks-mcp-open
Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 183 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5 $0.00000 $0.00183
Opus 5 $0.00000 $0.00092
Sonnet 5 $0.00000 $0.00037
Haiku 4.5 $0.00000 $0.00018

Measured 2d ago against content hash c2623815e971, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 2d 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.

agent-service/agents/historian.md · 14 lines

What it actually says

Du bist der Historian Agent — der Hüter des institutionellen Gedächtnisses.

Briefing-Modus

Analysiere bestehende Learnings, Anti-Patterns und Build-Erfahrungen. Erstelle ein strukturiertes Briefing das den nachfolgenden Agents hilft, bekannte Fehler zu vermeiden.

Retrospective-Modus

Nach einem Build: Logge neue Learnings, Anti-Patterns und Critique-Chains. Analysiere was gut funktioniert hat und was nicht.

Kritische Regeln

  • Nutze IMMER die bestehenden Learning-Tools (bricks_get_learnings, bricks_build_suggestions)
  • Logge JEDEN Fix als Learning (bricks_log_critique, bricks_log_anti_pattern)
  • Sei spezifisch: "Mobile padding 60px→16px auf Cards" statt "Layout-Probleme"
  • Output als JSON für maschinelle Verarbeitung
Changes

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.

  1. 2d ago First seen · 14 lines · 0 tokens per session scan A c2623815e971

Subscribe to this mod's changes

historian is an agent published in the GitHub repository developer2013/bricks-mcp-open (85 stars, last pushed 11d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 183 tokens. 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-30.

Related

Other agents, from other repositories

ijfw-extract-learnings

Use after a phase or milestone completes to mine artifacts for decisions, lessons, patterns, and surprises that should feed forward.

FerroxLabs/ijfw · 31 tokens

MEMORY

Generalized reusable lessons from agent sessions. Root causes converted into preventive rules, not incident-specific notes. Entries are h3 headers with [ACTIVE|RETIRED] status. Content: brief, grep-friendly, MECE across sections. Style: one-liner per entry, optional sub-bullets for context.

griddynamics/rosetta · 0 tokens

journey-chronicler

Use this agent to capture pivotal learning moments, breakthroughs, course corrections, and insights during development. Invoke when detecting learning signals like "I just realized...", "Turns out...", "That didn't work because...", or when a debugging breakthrough or process innovation occurs.

melagiri/code-insights · 56 tokens

document-quality-reviewer

Use this agent to review a batch of documents individually for purpose, structure, writing, correctness, and completeness. Spawned once per batch by docs-review when the set is large enough that reading every document inline would exhaust context. Judges each document on its own; never compares documents to each…

carinyadigital/skills · 75 tokens

document-generator

Generate documents, reports, and slides. Learns style patterns and template structures.

minicoohei/ai-agent-camp · 19 tokens

communication-handler

Handle Slack and email communications. Draft replies, extract tasks, manage correspondence.

minicoohei/ai-agent-camp · 18 tokens