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 FerroxLabs/ferrox-factory --skill ferrox-mempalace-recallgit 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/skills/ferroxlabs/ferrox-factory/ferrox-mempalace-recall)<a href="https://agentmods.dev/skills/ferroxlabs/ferrox-factory/ferrox-mempalace-recall"><img src="https://agentmods.dev/badge/skills/ferroxlabs/ferrox-factory/ferrox-mempalace-recall/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/ferroxlabs/ferrox-factory/ferrox-mempalace-recall"><img src="https://agentmods.dev/badge/skills/ferroxlabs/ferrox-factory/ferrox-mempalace-recall.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.00025 | $0.01510 |
| Opus 5 | $0.00013 | $0.00755 |
| Sonnet 5 | $0.00005 | $0.00302 |
| Haiku 4.5 | $0.00003 | $0.00151 |
Grade A, and why
ferrox-mempalace-recall 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 8d 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
91% identical to gsd-mempalace-recall — 19 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 — 107 lines — stays where its author put it; the contents beside it link to each section on GitHub.
STOP -- DO NOT READ THIS FILE. You are already reading it. This prompt was injected into your context by the command system. Using the Read tool on this file wastes tokens. Begin executing Step 0 immediately.
Step 0 -- Banner
Before ANY tool calls, display this banner:
Ferrox > MEMPALACE RECALL
Then proceed to Step 1.
Step 1 -- Config Gate
Check whether the MemPalace capability is enabled by reading .planning/config.json directly with the Read tool.
DO NOT use ferrox-tools config-get -- it hard-exits on missing keys unless --default is passed.
- Read
.planning/config.jsonwith the Read tool. - If the file does not exist: write the "unavailable" stub (Step 4) and STOP.
- Parse the JSON. Proceed to Step 2 only if
config.mempalace && config.mempalace.enabled === trueandconfig.mempalace.recall_on_plan !== false. Otherwise display the disabled message and STOP (recall_on_plan: falseturns plan-time recall off while leaving the rest of the capability enabled).
Disabled message:
Ferrox > MEMPALACE RECALL
MemPalace memory is disabled. To activate:
node <runtime-home>/ferrox-core/bin/ferrox-tools.cjs config-set mempalace.enabled true
Recall is opt-in; the loop proceeds normally without it.
This step is onError: skip at plan:pre -- recall never blocks planning.
Step 2 -- Resolve wing, mode, and transport
- Wing. Use
config.mempalace.wingif non-empty; otherwise derive fromconfig.project_code; otherwise fall back to the repository directory name. - Mode. Read
config.mempalace.memory_mode(augment|kg_backend|replace, defaultaugment). It sets how authoritative the palace is during recall:augment— the palace is an additional layer; read native memory (.planning/graphs/, STATE) too and treat the palace as supplementary.kg_backend— for knowledge-graph facts, query the palace's temporal KG first, as the primary source; fall back to.planning/graphs/when the palace is unreachable. Non-KG drawer recall stays additive.replace— resolve recall through the palace as the source of truth; consult native artifacts only as a fallback when the palace is unreachable. In every mode an unreachable palace degrades to native memory — recall never blocks (onError: skip).
- Transport. Prefer the MCP tools (
mempalace_*) in interactive runs when your MemPalace MCP server is registered and your runtime permits those tools. Otherwise — headless/cron/autonomous runs, or runtimes that don't grant the MemPalace MCP tools — use the CLI (mempalace wake-up,mempalace search), which this skill'sBashallow-tool always covers. If neither is reachable, go to Step 4. - Topic. Read the phase
CONTEXT.md(the consumed artifact). Derive a short search query from its title, goal, and key decisions.
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.
- 8d ago First seen · 107 lines · 25 tokens per session scan A 1ca254461556
ferrox-mempalace-recall is a skill published in the GitHub repository FerroxLabs/ferrox-factory (23 stars, last pushed 1mo ago), licensed MIT. It adds 25 tokens to every session and 1,510 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to gsd-mempalace-recall, differing in 19 lines, and is treated as a copy.
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.