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 regen-coordination/org-os-template --skill knowledge-curatorgit clone --depth 1 https://github.com/regen-coordination/org-os-templateWrote 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/regen-coordination/org-os-template/knowledge-curator)<a href="https://agentmods.dev/skills/regen-coordination/org-os-template/knowledge-curator"><img src="https://agentmods.dev/badge/skills/regen-coordination/org-os-template/knowledge-curator.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.00016 | $0.01752 |
| Opus 5 | $0.00008 | $0.00876 |
| Sonnet 5 | $0.00003 | $0.00350 |
| Haiku 4.5 | $0.00002 | $0.00175 |
Grade A, and why
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 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.
How it starts
The opening of the file, as written. The whole thing — 229 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Knowledge Curator
What This Is
Monitors organizational channels (Telegram, GitHub, meeting notes) for meaningful knowledge, organizes it by domain, and produces curated summaries for the workspace and federation commons. Turns the constant flow of shared links and discussions into navigable organizational knowledge.
When to Use
- When asked "what do we know about [topic]?"
- When Telegram groups have accumulated links and updates to process
- After meetings where domain knowledge was discussed
- Weekly: scheduled curation of accumulated knowledge
- When preparing a thematic report or discussion
When NOT to Use
- For individual meeting processing → use meeting-processor skill
- For financial tracking → use capital-flow skill
- For raw transcript processing → use meeting-processor skill
Inputs
- Telegram channel messages (if channel access is configured in
TOOLS.md) - Meeting notes in
packages/operations/meetings/ - GitHub activity from monitored repos (configured in
TOOLS.md) - Direct content pasted by operator
- Knowledge gaps flagged by the graph in
data/knowledge-gaps.yaml(triage workflow inskills/knowledge-graph/SKILL.md)
Outputs
| Output | Location | Format |
|---|---|---|
| Domain curation | knowledge/<domain>/YYYY-MM-DD.md |
Markdown |
| Hub contribution | Sync to hub knowledge/ |
Markdown |
| Weekly digest | memory/YYYY-MM-DD.md |
Markdown |
| Memory index update | MEMORY.md |
Markdown |
What Gets Curated
High Value (always curate)
- Funding opportunities and platform mechanics
- Partner organization updates (new projects, launches, pivots)
- Governance decisions from ecosystem protocols
- Technical developments relevant to org domains
- Strategic insights from discussions
Medium Value (curate if distinct)
- Shared links with substantive context
- Questions with useful answers
- Project status updates from network
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 · 229 lines · 16 tokens per session scan A 2c03d70ab14d
knowledge-curator is a skill published in the GitHub repository regen-coordination/org-os-template (5 stars, last pushed yesterday), licensed MIT. It adds 16 tokens to every session and 1,752 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 skills, from other repositories
wegent-knowledge
Knowledge base management and search tools for Wegent. Provides capabilities to list, create, update, and search knowledge bases and documents using RAG retrieval. Use this skill when the user wants to manage knowledge bases, documents, or search for information programmatically.
knowledge_base
Manage the user's personal knowledge base — knowledge graph, documents, and wiki vault.
openlore
Query and publish to an OpenLore knowledge base over SSH using ordinary shell commands. Use when a task needs project documentation, runbooks, shared team knowledge, or a place to publish findings.
openlore-housekeeping
Audit and maintain a shared OpenLore knowledge base. Use on a schedule or on request to find stale docs, broken links, unreviewed inbox items, and missing skill coverage, then publish an audit report.
continuous-learning
Use when a mistake, correction, or surprise taught the workspace something that must stick — a retro or postmortem, the same agent error corrected twice, a resolved bug's root cause, scattered notes-to-self — and route that lesson to the durable surface that fires next time. NOT a forward choice with alternatives…
brain-sync
Sync knowledge and learnings to the shared appie-brain repo. Every Appie commits with their own identity so contributions are traceable. Use after: complex tasks (5+ tool calls), significant discoveries, new skills, or client work. Fleet: Appie-1 (Orchestrator/MacMini), Appie-2 (CMO/DO), Appie-3 (CTO/VPS).