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/FerroxLabs/ferrox-factoryWrote 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/ferroxlabs/ferrox-factory/ferrox-mempalace-curator)<a href="https://agentmods.dev/agents/ferroxlabs/ferrox-factory/ferrox-mempalace-curator"><img src="https://agentmods.dev/badge/agents/ferroxlabs/ferrox-factory/ferrox-mempalace-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/ferroxlabs/ferrox-factory/ferrox-mempalace-curator"><img src="https://agentmods.dev/badge/agents/ferroxlabs/ferrox-factory/ferrox-mempalace-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.00059 | $0.01097 |
| Opus 5.5 | $0.00024 | $0.00439 |
| Sonnet 5.5 | $0.00012 | $0.00219 |
| Haiku 4.5 | $0.00006 | $0.00110 |
Grade A, and why
ferrox-mempalace-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.
This is a copy
88% identical to gsd-mempalace-curator — 12 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 48 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Gate
If mempalace.enabled !== true, do nothing and report MemPalace disabled — curation skipped. This is the hard gate; respect it before any other work.
Wing / mode / transport
- Wing:
mempalace.wingif non-empty, elseproject_code, else the repo directory name. Every call you make is scoped to this one wing. - Mode (
mempalace.memory_mode): underaugment, KG writes are an additive mirror of.planning/graphs/. Underkg_backend/replace, the palace KG is the authoritative fact store — still mirror every fact here as the primary target; Ferrox's normal graphify keeps.planning/graphs/current, so an unreachable palace never loses history. - Transport: prefer the
mempalace_*MCP tools interactively; fall back to themempalaceCLI in headless/cron runs. If neither is reachable, report unavailability and stop — do not error.
Tasks (each independently best-effort)
- Diary entry (when
mempalace.diary_journalis true). Write one concise per-agent diary entry summarising the phase outcome:mempalace_diary_write(agent_name=<project>/<role>, entry=<summary>, topic="phase-ship", wing=<wing>)(CLI:mempalace hook run/ the diary CLI). Namespaceagent_nameby repo+role so diaries don't collide across projects. Idempotency: before writing,mempalace_diary_read(or list) for an existing entry keyed by(wing, agent_name, topic, phase-id); if one exists for this phase, update it in place rather than appending a second.
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 · 48 lines · 59 tokens per session scan A 862d6ed888f1
ferrox-mempalace-curator is an agent published in the GitHub repository FerroxLabs/ferrox-factory (23 stars, last pushed 2mo ago), licensed MIT. It adds 59 tokens to every session and 1,097 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 88% identical to gsd-mempalace-curator, differing in 12 lines, and is treated as a copy.
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.
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.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.