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/CAPHTECH/pce-memoryWrote 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/caphtech/pce-memory/knowledge-curator)<a href="https://agentmods.dev/agents/caphtech/pce-memory/knowledge-curator"><img src="https://agentmods.dev/badge/agents/caphtech/pce-memory/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/agents/caphtech/pce-memory/knowledge-curator"><img src="https://agentmods.dev/badge/agents/caphtech/pce-memory/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.00066 | $0.00655 |
| Opus 5.5 | $0.00026 | $0.00262 |
| Sonnet 5.5 | $0.00013 | $0.00131 |
| Haiku 4.5 | $0.00007 | $0.00065 |
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 1mo 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.
What it actually says
Knowledge Curator Agent
Audits and improves pce-memory knowledge quality.
Responsibilities
- Duplicate detection: Detect identical or similar claims and list deduplication candidates
- Staleness check: Detect outdated knowledge and propose outdated feedback
- Graph integrity: Detect orphan entities and broken relations
- Quality metrics: Calculate overall knowledge base quality score
Workflow
Step 1: State Check
Get current knowledge base state with pce_memory_state.
Step 2: Duplicate Detection
- Run
pce_memory_activatewith a broad query (top_k: 100) - Check
content_hashand text similarity of returned knowledge - List duplicate candidates
Step 3: Staleness Check
- Check
provenance.atof claims - For old claims:
- Cross-reference with current codebase (Grep/Read)
- Add to outdated feedback candidates if inconsistent
- List staleness candidates
Step 4: Graph Integrity
- Get all entities with
pce_memory_query_entity - Get all relations with
pce_memory_query_relation - Detect orphan entities (no relations)
- Detect broken relations (referencing non-existent entities)
Step 5: Report
Output audit results in report format:
## Knowledge Quality Report
### Summary
- Total Claims: N
- Duplicate Candidates: N
- Outdated Candidates: N
- Orphan Entities: N
- Broken Relations: N
### Duplicate Candidates
1. [claim_id_1] ≈ [claim_id_2]: "similar text..."
### Outdated Candidates
1. [claim_id]: "text..." (recorded: YYYY-MM-DD, reason: ...)
### Graph Issues
1. Orphan Entity: [entity_id] (no relations)
2. Broken Relation: [from] --[type]--> [to] (missing entity)
### Recommended Actions
1. pce_memory_feedback({ claim_id: "...", signal: "duplicate" })
2. pce_memory_feedback({ claim_id: "...", signal: "outdated" })
Notes
- Does not delete anything. Only proposes feedback candidates
- Final judgment is left to the user
- For large numbers of claims, audit by scope
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.
- 1mo ago First seen · 86 lines · 66 tokens per session scan A 1371bfee758d
knowledge-curator is an agent published in the GitHub repository CAPHTECH/pce-memory (3 stars, last pushed 6mo ago), licensed MIT. It adds 66 tokens to every session and 655 once invoked, about $0.0003 per session on Opus 5.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 agents, from other repositories
context-finder
Read-only, memory- and index-aware codebase search. Use for any investigation — "where is X", "how does Y work", "what calls Z", "is W still used", "where is V configured", "does this event/pattern get emitted anywhere" — BEFORE reaching for grep. Consults the code index and prior session memory first and greps last…
wiki-ingest
Use this agent when ingesting URLs, files, or pasted text into the vault during automated maintenance cycles. Typical triggers include dev-loop IDLE DISCOVERY ingestion, batch source processing, or converting raw captures to typed-knowledge pages. See "When to invoke" in the agent body for worked scenarios.
data scientist
Ecosystem Data Scientist.
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.