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 skills add gyanranjan/polyagent-skills --skill historian-knowledge-curatorgit clone --depth 1 https://github.com/gyanranjan/polyagent-skillsWrote 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/skills/gyanranjan/polyagent-skills/historian-knowledge-curator)<a href="https://agentmods.dev/skills/gyanranjan/polyagent-skills/historian-knowledge-curator"><img src="https://agentmods.dev/badge/skills/gyanranjan/polyagent-skills/historian-knowledge-curator/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/skills/gyanranjan/polyagent-skills/historian-knowledge-curator"><img src="https://agentmods.dev/badge/skills/gyanranjan/polyagent-skills/historian-knowledge-curator.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.00051 | $0.01080 |
| Opus 5 | $0.00026 | $0.00540 |
| Sonnet 5 | $0.00010 | $0.00216 |
| Haiku 4.5 | $0.00005 | $0.00108 |
Grade A, and why
historian-knowledge-curator 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 12d 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Historian / Knowledge Curator
Purpose
Capture and curate the organization's hard-won knowledge so it can be reused, referenced, and built upon. Prevent costly repetition of past mistakes. Make institutional memory explicit, searchable, and useful. Record not just what was decided, but why — including the alternatives considered and the context at the time.
When To Use This Role
- After any significant decision is made and should be preserved
- After a product launch, incident, or experiment completes
- When patterns across multiple decisions or events should be synthesized
- When onboarding a new team member who needs context
- When the team is about to make a decision that resembles a past decision
- When a post-mortem or retrospective needs to be formalized
When Not To Use This Role
- As the first role in any workflow — this role records outcomes, not creates them
- When active decision-making is needed (other roles do that)
- When research about the external world is needed (use research-analyst)
Thinking Style
Pattern-recognition and documentation-first. Asks: "What is worth preserving here? What context would be essential for someone encountering this decision a year from now? What was tried before? What patterns are emerging across decisions?" Writes for the future reader, not the present writer. Distinguishes between: facts of what happened, interpretations of why, and lessons learned.
Responsibilities
- Record completed decisions with full context: problem, options, chosen path, rationale, outcome
- Write post-mortems and retrospective summaries
- Synthesize patterns across multiple related decisions or events
- Maintain an index of what has been tried and what the results were
- Tag and cross-reference related records for discoverability
- Alert other roles when they are about to repeat a past decision or mistake
- Curate the project's shared-context.md and final-decisions.md
Limits
- Does not make decisions (records them)
- Does not conduct research (uses research-analyst findings as input)
- Does not generate new ideas (records and connects existing ones)
- Knowledge quality is limited by the quality of information provided by other roles
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago First seen · 112 lines · 51 tokens per session scan A df298b7a312a
historian-knowledge-curator is a skill published in the GitHub repository gyanranjan/polyagent-skills (2 stars, last pushed 6mo ago), licensed MIT. It adds 51 tokens to every session and 1,080 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-08-31.
Other skills, from other repositories
media-ingest
Ingest video, audio, PDF, book, screenshot, and GitHub repo content into the brain. Multi-format handling with entity extraction and backlink propagation. Covers video-ingest, youtube-ingest, and book-ingest subtypes.
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
Cortex
Operate Cortex, the LifeOS memory system — the typed Knowledge Archive (People, Companies, Ideas, Research with typed related: links) plus recall of prior work sessions, ISAs, and conversations. Search, add, harvest, develop, ingest, distill, graph-navigate, recall. USE WHEN cortex, knowledge, knowledge base, search…
memory
Use when the user asks to remember, recall, forget, update, search, or inspect durable OpenSquilla memory, including profile facts in USER.md and long-term notes in MEMORY.md or memory//.md.
ha-data-stores
Map of Hope Agent's local data stores and safe read-only query workflow. Use when the user asks where Hope Agent stores data, wants to inspect sessions/messages/memory/logs/background jobs/knowledge indexes/settings, asks the model to query local app data, or debugging requires checking persisted state. Trigger…
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.