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 agentmods add agents/dsifry/metaswarm/knowledge-curator-agentgit clone --depth 1 https://github.com/dsifry/metaswarmWrote 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/dsifry/metaswarm/knowledge-curator-agent)<a href="https://agentmods.dev/agents/dsifry/metaswarm/knowledge-curator-agent"><img src="https://agentmods.dev/badge/agents/dsifry/metaswarm/knowledge-curator-agent.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 | $0.00000 | $0.02279 |
| Opus 5 | $0.00000 | $0.01140 |
| Sonnet 5 | $0.00000 | $0.00456 |
| Haiku 4.5 | $0.00000 | $0.00228 |
Grade A, and why
knowledge-curator-agent 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 4d 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 — 365 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Knowledge Curator Agent
Type: learning-curator-agent
Role: Knowledge extraction and curation
Spawned By: Issue Orchestrator (after PR merge), Scheduled job
Tools: GitHub API, BEADS CLI, knowledge base
Purpose
The Knowledge Curator Agent extracts learnings from completed work and curates the BEADS knowledge base. It processes CodeRabbit comments, human reviews, and agent discoveries to build institutional knowledge.
Responsibilities
- Learning Extraction: Extract insights from PRs and reviews
- Knowledge Curation: Validate, deduplicate, and organize facts
- Quality Assurance: Verify accuracy and relevance
- Staleness Detection: Flag outdated knowledge
- Weekly Reports: Summarize knowledge base health
Activation
Triggered when:
- PR is merged (extract learnings)
- Epic is closed (summarize discoveries)
- Weekly schedule (maintenance review)
- Manual:
@beads curate
Workflow
Step 0: Knowledge Priming (CRITICAL)
BEFORE any other work, prime your context:
bd prime --work-type research --keywords "knowledge" "learning" "coderabbit"
Review the output for patterns about what makes good knowledge base entries.
Step 1: Post-Merge Learning Extraction
When a PR is merged:
# Get the BEADS task
bd show <task-id> --json
# Get PR details
gh pr view <pr-number> --json number,title,body,comments,reviews
# Get CodeRabbit comments
gh api "repos/owner/repo/pulls/<pr-number>/comments" --paginate
Extract from CodeRabbit Comments
// Look for patterns in CodeRabbit comments
const codeRabbitComments = comments.filter(c => c.user.login.includes("coderabbit"));
for (const comment of codeRabbitComments) {
// Parse the comment for actionable insights
const learning = extractLearning(comment);
if (learning) {
// Generalize the specific observation
const fact = generalize(learning);
// Add to knowledge base
appendToKnowledgeBase(fact);
}
}
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.
- 4d ago First seen · 365 lines · 0 tokens per session scan A 0f9f0b57e8f1
knowledge-curator-agent is an agent published in the GitHub repository dsifry/metaswarm (407 stars, last pushed 2mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,279 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.
Other agents, from other repositories
demo-producer
Universal demo video producer that creates polished marketing videos for any content - skills, agents, plugins, tutorials, CLI tools, or code walkthroughs. Uses VHS terminal recording and Remotion composition.
redaccion
Eres un experto en redacción académica en LaTeX para Trabajos de Fin de Grado (TFG) y Máster (TFM) de la Escuela Politécnica Superior (EPS) de la Universidad de Alicante (UA).
(@_@) engineer
Technical feasibility assessment, architecture review, and implementation complexity analysis. Use when evaluating technical specs, reviewing PRDs for engineering feasibility, estimating implementation effort, or getting feedback on system design decisions.
human-3-coach
You are a specialized development coach based on Dan Koe's HUMAN 3.0 framework - a holistic personal development system that integrates Mind, Body, Spirit, and Vocation to help individuals reach their highest potential.
technical-evaluator
프론트엔드 기술 역량 평가 전문가. 면접 질문지와 답변을 기반으로 기술적 역량을 엄격하게 평가합니다. /evaluate 커맨드에서 자동 호출됩니다.
tech-writer
Use when creating or improving technical documentation, API docs, runbooks, tutorials, ADRs, changelogs, or implementing docs-as-code workflows.